From: Daniel Phillips <phillips@bonn-fries.net>
To: Andrew Morton <akpm@zip.com.au>,
Bob McElrath <mcelrath+linux@draal.physics.wisc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: low-latency patches
Date: Sat, 6 Oct 2001 18:33:42 +0200 [thread overview]
Message-ID: <20011006163412Z16352-2758+1299@humbolt.nl.linux.org> (raw)
In-Reply-To: <20011006010519.A749@draal.physics.wisc.edu> <3BBEA8CF.D2A4BAA8@zip.com.au>
In-Reply-To: <3BBEA8CF.D2A4BAA8@zip.com.au>
On October 6, 2001 08:46 am, Andrew Morton wrote:
> Bob McElrath wrote:
> > 1) Which of these two projects has better latency performance? Has anyone
> > benchmarked them against each other?
>
> I haven't seen any rigorous latency measurements on Rob's stuff, and
> I haven't seriously measured the reschedule-based patch for months. But
> I would expect the preempt patch to perform significantly worse because
> it doesn't attempt to break up the abovementioned long-held locks.
Nor should it. The preemption patch should properly address only what is
needed to implement preemption, and a patch similar to yours should be
applied on top to break up the remaining lock latencies. (Perhaps a duh?)
> (It can
> do so, though - a straightforward adaptation of the reschedule patch's
> changes will fix it).
Yep.
--
Daniel
next prev parent reply other threads:[~2001-10-06 16:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 6:05 Bob McElrath
2001-10-06 6:46 ` Andrew Morton
2001-10-06 16:33 ` Daniel Phillips [this message]
2001-10-06 20:42 ` Bob McElrath
2001-10-06 22:00 ` Mike Fedyk
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-06 22:22 ` Robert Love
2001-10-06 22:36 ` Robert Love
2001-10-06 22:46 ` Mike Fedyk
2001-10-07 1:12 ` Robert Love
2001-10-07 2:38 ` Jeffrey W. Baker
2001-10-07 2:55 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 15:27 David Balazic
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=20011006163412Z16352-2758+1299@humbolt.nl.linux.org \
--to=phillips@bonn-fries.net \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mcelrath+linux@draal.physics.wisc.edu \
/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
all inboxes | Powered by JetHome®