Re: interrupt latency and driver locking
From: M. Warner Losh (imp_at_bsdimp.com)
Date: 09/21/03
- Previous message: John Polstra: "Re: interrupt latency and driver locking"
- In reply to: John Polstra: "Re: interrupt latency and driver locking"
- Next in thread: John Polstra: "Re: interrupt latency and driver locking"
- Reply: John Polstra: "Re: interrupt latency and driver locking"
- Reply: Harti Brandt: "Re: interrupt latency and driver locking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 20 Sep 2003 21:48:35 -0600 (MDT) To: jdp@polstra.com
In message: <XFMail.20030920142934.jdp@polstra.com>
John Polstra <jdp@polstra.com> writes:
: there will be no link changes except at bootstrap and shutdown.
For server machines. For laptops, these events happen more often.
However, for most laptops, the rate that they happen is typically on
less than 1/hour. Still rare enough to not worry about optimizing it
and your other points are good. I just wanted to make sure that it
wasn't optimized to the point where disconnecting the cable from the
laptop to move it accross the room, or another room doesn't cause huge
problems.
Warner
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: John Polstra: "Re: interrupt latency and driver locking"
- In reply to: John Polstra: "Re: interrupt latency and driver locking"
- Next in thread: John Polstra: "Re: interrupt latency and driver locking"
- Reply: John Polstra: "Re: interrupt latency and driver locking"
- Reply: Harti Brandt: "Re: interrupt latency and driver locking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
