From: Andrew Morton <akpm@zip.com.au>
To: Robert Love <rml@tech9.net>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-ac5-preempt, overflow in cached memory stat?
Date: Mon, 05 Nov 2001 00:37:55 -0800 [thread overview]
Message-ID: <3BE64FE3.DBEF8E21@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0111051019080.6741-100000@netfinity.realnet.co.sz>, <Pine.LNX.4.33.0111051019080.6741-100000@netfinity.realnet.co.sz> <1004948146.806.4.camel@phantasy>
Robert Love wrote:
>
> > PS I know you keep hearing this, but that preempt patch makes for some
> > damn smooth interactive performance ;)
>
> I can't hear it enough :)
>
umm... Look. Sorry. But I don't see any theoretical reason
why interactivity should be noticeably different from the
little patch at
http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.14pre7aa2/00_lowlatency-fixes-2
and I did some quantitative testing a week or so back which
bears this out. With either patch, worst-case latencies
are very rare, and very bad. Usual latencies are excellent.
Is there any reason why preempt should be noticeably better than
that little patch? If it is, then where on earth are the
problematic commonly-occuring, long-running, lock-free code paths?
-
next prev parent reply other threads:[~2001-11-05 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-03 9:51 2.4.13-ac5-preempt, overflow in cached memory stat? Zwane Mwaikambo
2001-11-05 7:56 ` Robert Love
2001-11-05 8:21 ` Zwane Mwaikambo
2001-11-05 8:15 ` Robert Love
2001-11-05 8:37 ` Andrew Morton [this message]
2001-11-05 9:14 ` Zwane Mwaikambo
2001-11-05 17:20 ` Andrea Arcangeli
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=3BE64FE3.DBEF8E21@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=zwane@linux.realnet.co.sz \
/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