From: Robert Love <rml@tech9.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>,
"Andrea Arcangeli" <andrea@suse.de>
Subject: Re: latency & real-time-ness.
Date: 04 Mar 2002 18:56:57 -0500 [thread overview]
Message-ID: <1015286218.1083.21.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44L.0203042047010.2181-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.44L.0203042047010.2181-100000@imladris.surriel.com>
On Mon, 2002-03-04 at 18:48, Rik van Riel wrote:
> > If rmap finds its way into 2.5, I and others have some ideas about ways
> > to optimize the algorithms to reduce lock hold time and benefit from
> > preemption. For example, Daniel Phillips has some ideas wrt
> > zap_page_range.
>
> Feel free to help resolve these issues before rmap code gets
> merged. I'd prefer to be able to introduce rmap in small bits
> and pieces without breaking anything.
The above was just an optimization ... rmap and preempt work fine
together.
What Andrew Morton, I, and others intend to do for 2.5 is work on the
algorithms and locking issues to work on latency issues cleanly.
But I'll surely work on the issues wrt rmap ;)
Robert Love
next prev parent reply other threads:[~2002-03-04 23:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 16:20 latency & real-time-ness Dieter Nützel
2002-03-04 18:32 ` Robert Love
2002-03-04 23:48 ` Rik van Riel
2002-03-04 23:56 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-03 20:12 Ben Greear
2002-03-03 20:55 ` Alan Cox
2002-03-03 22:43 ` Ben Greear
2002-03-04 1:12 ` J Sloan
2002-03-04 3:32 ` Ben Greear
2002-03-04 3:45 ` Robert Love
2002-03-04 4:32 ` J Sloan
2002-03-04 20:01 ` Jussi Laako
2002-03-04 1:09 ` J Sloan
2002-03-04 1:33 ` Alan Cox
2002-03-04 1:37 ` J Sloan
2002-03-04 15:31 ` Erik Andersen
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=1015286218.1083.21.camel@phantasy \
--to=rml@tech9.net \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riel@conectiva.com.br \
/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