From: Fabio Riccardi <fabio@chromium.com>
To: Jens Axboe <axboe@kernel.org>
Cc: "Leeuw van der, Tim" <tim.leeuwvander@nl.unisys.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.5-ac2
Date: Tue, 29 May 2001 16:55:08 -0700 [thread overview]
Message-ID: <3B1436DC.60869CFB@chromium.com> (raw)
In-Reply-To: <DD0DC14935B1D211981A00105A1B28DB033ED2F0@NL-ASD-EXCH-1> <3B13542A.5DBA3903@chromium.com> <20010529121954.J26871@suse.de>
yes I get a performance improvement of about 5%
could you port your patches to the 2.4.5-ac4 kernel? I'd love to see if the ac
improvements and yours add to each other.
Thanks,
- Fabio
Jens Axboe wrote:
> On Tue, May 29 2001, Fabio Riccardi wrote:
> > "Leeuw van der, Tim" wrote:
> >
> > > But the claim was that 2.4.5-ac2 is faster than 2.4.5 plain, so which
> > > changes are in 2.4.5-ac2 that would make it faster than 2.4.5 plain? Also, I
> > > don't know if 2.4.5-ac1 is as fast as 2.4.5-ac2 for Fabio. If not, then it's
> > > a change in the 2.4.5-ac2 changelog. If it is as fast, it is one of the
> > > changes in the 2.4.5-ac1 changelog.
> >
> > 2.4.5-ac1 crashed on my machine, vanilla 2.4.5 worked but slower than 2.4.2
> >
> > 2.4.5-ac2 is _a lot_ faster than all the 2.4.4 and of vanilla 2.4.5
> >
> > please notice that I have a 4G machine, dual proc, and I run a very
> > memory/IO/CPU intensive test, so your mileage may vary with different
> > applications.
>
> Could you try the 4GB I/O patches and see if they boost performance of
> such cases?
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5/
>
> --
> Jens Axboe
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-05-29 23:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 15:19 Linux 2.4.5-ac2 Leeuw van der, Tim
2001-05-28 16:20 ` Alan Cox
2001-05-28 20:49 ` Mike Galbraith
2001-05-28 19:38 ` Marcelo Tosatti
2001-05-28 21:42 ` André Dahlqvist
2001-05-28 22:10 ` André Dahlqvist
2001-05-28 21:15 ` Marcelo Tosatti
2001-05-28 23:44 ` André Dahlqvist
2001-05-29 4:57 ` Mike Galbraith
2001-05-29 7:47 ` Fabio Riccardi
2001-05-29 10:19 ` Jens Axboe
2001-05-29 23:55 ` Fabio Riccardi [this message]
2001-05-30 9:29 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2001-05-28 0:33 Alan Cox
2001-05-28 3:38 ` Tom Vier
2001-05-28 5:32 ` Tom Vier
2001-05-28 3:44 ` Fabio Riccardi
2001-05-28 13:37 ` Alan Cox
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=3B1436DC.60869CFB@chromium.com \
--to=fabio@chromium.com \
--cc=axboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.leeuwvander@nl.unisys.com \
/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