From: "Paolo Ciarrocchi" <ciarrocchi@linuxmail.org>
To: conman@kolivas.net, linux-kernel@vger.kernel.org
Subject: Re: Combined performance patches update for 2.4.19
Date: Sun, 25 Aug 2002 02:58:38 +0800 [thread overview]
Message-ID: <20020824185838.2961.qmail@linuxmail.org> (raw)
From: conman@kolivas.net
Date: Sat, 24 Aug 2002 22:21:37 +1000
> > > > BTW, thank you for your great work!!
> > >
> > > My pleasure, but really the hard work is done by the developers!
> > Sure, but your "performance" approach is really intersting! Do you use a
> > benchmark?
>
> I don't really have the time to benchmark these things any more than "it feels
> faster". Really I'm spending way too much time on this as it is and I'm not
> remotely any authority on what benchmarks to use.
Maybe I can find the time to run a few tests, can anyone suggest me an "intersting" test?
> > > > I'm also testing the compressed cache (the
> > > > patch you've discarded, and I got good performance!)
> > >
> > > I'm thinking of eventually merging the latest version of this into 2.4.19
> > too
> > > since it can be enabled or disabled. Depends on the demand.
> > Just an hint ('cause I made some of the test you can see on the compressed
> > cache web page on sourceforge),
> > if you use that patch boot your box with the
> > compressed=XXM in order to set the amount of the compressed cache. My box
> > runs fast and happy with 32MiB or 64MiB of compressed cache. My box has
> > 256MiB of Ram.
>
> Ok thanks for the info. I believe the newer cc patch (not in my 2.4.18-ck4) is
> better anyway. I'm afraid the cc will be later in the piece assuming I can kill
> off the other bug I've created in the merge. I'd prefer to see a cc patch
> specifically for 2.4.19 as forward porting it to .19 and then to O(1) (and so
> on) are just too many steps.
Fair enough.
I think that soon we'll see the cc path for the 2.4.19, Rodrigo?
Ciao,
Paolo
--
Get your free email from www.linuxmail.org
Powered by Outblaze
next reply other threads:[~2002-08-24 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 18:58 Paolo Ciarrocchi [this message]
2002-08-24 20:56 ` Combined performance patches update for 2.4.19 Rik van Riel
2002-08-27 22:48 ` Cliff White
-- strict thread matches above, loose matches on Subject: below --
2002-08-25 12:33 Paolo Ciarrocchi
[not found] <20020824120208.30967.qmail@linuxmail.org>
2002-08-24 12:21 ` conman
[not found] <20020823233128.20631.qmail@linuxmail.org>
2002-08-24 0:53 ` conman
[not found] <Pine.LNX.4.44L.0208231012530.1857-100000@imladris.surriel.com>
2002-08-23 14:10 ` conman
2002-08-23 15:52 ` Rik van Riel
2002-08-23 12:38 conman
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=20020824185838.2961.qmail@linuxmail.org \
--to=ciarrocchi@linuxmail.org \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.