From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: Robert Love <rml@tech9.net>,
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, 5 Nov 2001 18:20:47 +0100 [thread overview]
Message-ID: <20011105182047.E18319@athlon.random> (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> <3BE64FE3.DBEF8E21@zip.com.au>
In-Reply-To: <3BE64FE3.DBEF8E21@zip.com.au>; from akpm@zip.com.au on Mon, Nov 05, 2001 at 12:37:55AM -0800
On Mon, Nov 05, 2001 at 12:37:55AM -0800, Andrew Morton wrote:
> 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
indeed, the only thing that PE can really change is the mean latency but
everbody only cares about worst case latency and nominal performance,
possibly except realtime signal processing (not multimedia playback
like listening mp3).
Andrea
prev parent reply other threads:[~2001-11-05 17:22 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
2001-11-05 9:14 ` Zwane Mwaikambo
2001-11-05 17:20 ` Andrea Arcangeli [this message]
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=20011105182047.E18319@athlon.random \
--to=andrea@suse.de \
--cc=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