From: David Balazic <david.balazic@uni-mb.si>
To: alan@lxorguk.ukuu.org.uk,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: low-latency patches
Date: Wed, 10 Oct 2001 17:27:09 +0200 [thread overview]
Message-ID: <3BC468CD.5A2C8FF4@uni-mb.si> (raw)
Alan Cox (alan@lxorguk.ukuu.org.uk) wrote :
> > Right. It needs to be a conscious, planned decision: "from now on,
> > holding a lock for more than 500 usecs is a bug".
>
> Firstly you can start with "of course some hardware will stall the bus
> longer than that"
So ?
Some hardware miscalculates certain floating point operations,
but we still use FPUs.
Some ethernet cards corrupt the packets, but Linux still supports ethernet.
Some IDE hardrives lock up in DMA mode, yet Linux still supports DMA.
Some softmodems don't work at all, yet Linux still support modems.
There is always buggy hardware in every category. No reason to not use the good ones.
david, just being a PITA ...
--
David Balazic
--------------
"Be excellent to each other." - Bill S. Preston, Esq., & "Ted" Theodore Logan
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
next reply other threads:[~2001-10-10 15:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 15:27 David Balazic [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-06 6:05 low-latency patches Bob McElrath
2001-10-06 6:46 ` Andrew Morton
2001-10-06 16:33 ` Daniel Phillips
2001-10-06 20:42 ` Bob McElrath
2001-10-06 22:00 ` Mike Fedyk
2001-10-06 22:22 ` Robert Love
2001-10-08 12:47 ` Helge Hafting
2001-10-08 17:41 ` george anzinger
2001-10-08 18:24 ` Andrew Morton
2001-10-08 18:36 ` Alan Cox
2001-10-07 1:12 ` Robert Love
2001-10-07 2:38 ` Jeffrey W. Baker
2001-10-07 2:55 ` Robert Love
2001-10-06 22:36 ` Robert Love
2001-10-06 22:46 ` Mike Fedyk
2001-03-08 13:06 Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BC468CD.5A2C8FF4@uni-mb.si \
--to=david.balazic@uni-mb.si \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox