From: Robert Love <rml@tech9.net>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: 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 13:32:28 -0500 [thread overview]
Message-ID: <1015266757.15277.4.camel@phantasy> (raw)
In-Reply-To: <200203041720.41169.Dieter.Nuetzel@hamburg.de>
In-Reply-To: <200203041720.41169.Dieter.Nuetzel@hamburg.de>
On Mon, 2002-03-04 at 11:20, Dieter Nützel wrote:
> Robert I am running 2.4.19-pre2-ac2 + preemption + lock-break.
> It is very snappy due to lock-break I think.
> But lock-break failed on vmscan.c and I didn't apply it by hand this time.
> There was another fail but it was small and easily fixable.
> We need a new lock-break, soon.
-ac2 has rmap and lock-break is not designed for the rmap VM. You can
just ignore the rejects. Further, rmap has some conditional schedules
so you are taken care of.
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.
> Sadly it is relative hard to put sched-O1-2.4.18-pre8-K3.patch and preemption
> on top of 2.4.19pre2aa1 which I did for several weeks before. The throughput
> with -aa VM maintenance is much better then with -ac.
>
> Latest -aa is 2.4.18-pre8-K3-VM-24-preempt-lock.
Robert Love
next prev parent reply other threads:[~2002-03-04 18:33 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 [this message]
2002-03-04 23:48 ` Rik van Riel
2002-03-04 23:56 ` Robert Love
-- 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=1015266757.15277.4.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 \
/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