From: Oleg Drokin <green@namesys.com>
To: Philippe Gramoulle <philippe.gramoulle@mmania.com>
Cc: ReiserFS Mailing List <reiserfs-list@namesys.com>
Subject: Re: Speedup patch for 2.4.19-pre6 in bitmap.c
Date: Wed, 10 Apr 2002 19:13:56 +0400 [thread overview]
Message-ID: <20020410191356.A22756@namesys.com> (raw)
In-Reply-To: <20020410170919.G54344@off.aspic.com>
Hello!
On Wed, Apr 10, 2002 at 05:09:19PM +0200, Philippe Gramoulle wrote:
> > So I assume you are negatively surprised, right?
> > And if you undo the speedup patch only, do you get your numbers back?
> > Also do you have highmem on for 2.4.19-pre6 kernel?
> Sorry for the confusion :
> With 2.4.18 + TCP patch => 10Mb/s
> Now witout the speedup patch and with a 2.4.19-pre6 + the patches i've listed => 6.32 Mb/s NFS TCP
> That's why i want to give your speedup patch a try !! :o)
Ah. So my question remains, do you have highmem enabled? If you do,
also try without highmem with and without speedup patches.
Number of peoples raised a question about Andrea Archangelli's patch
that went into 2.4.19-pre5 to improve I/O throughtput wrt several allocation
zones.
I myself see throughtput decrease with highmem on.
> i'll redo the test, time for me to rebuild the kernel with the speedup patch and redo the tests, say 15minutes.
> I' send the figures then.
Ok. Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2002-04-10 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 14:55 Speedup patch for 2.4.19-pre6 in bitmap.c Philippe Gramoulle
2002-04-10 15:02 ` Oleg Drokin
2002-04-10 15:09 ` Philippe Gramoulle
2002-04-10 15:13 ` Oleg Drokin [this message]
2002-04-10 18:48 ` Philippe Gramoulle
2002-04-10 19:05 ` Oleg Drokin
2002-04-10 19:09 ` Philippe Gramoulle
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 15:04 wolfgang.glas
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=20020410191356.A22756@namesys.com \
--to=green@namesys.com \
--cc=philippe.gramoulle@mmania.com \
--cc=reiserfs-list@namesys.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 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.