From: Maneesh Soni <smaneesh@in.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: tridge@samba.org, lkml <linux-kernel@vger.kernel.org>,
lse tech <lse-tech@lists.sourceforge.net>
Subject: Re: [Lse-tech] Re: [RFC][PATCH] Scalable FD Management using Read-Copy-Update
Date: Thu, 12 Apr 2001 21:13:54 +0530 [thread overview]
Message-ID: <20010412211354.A25905@in.ibm.com> (raw)
In-Reply-To: <20010409201311.D9013@in.ibm.com> <20010411182929.A16665@va.samba.org>
In-Reply-To: <20010411182929.A16665@va.samba.org>; from anton@samba.org on Wed, Apr 11, 2001 at 06:29:30PM -0700
On Wed, Apr 11, 2001 at 06:29:30PM -0700, Anton Blanchard wrote:
>
> > This patch provides a very good performance improvement in file
> > descriptor management for SMP linux kernel on a 4-way machine with the
> > expectation of even higher gains on higher end machines. The patch uses the
> > read-copy-update mechanism for Linux, published earlier at the sourceforge
> > site under Linux Scalablity Effort project.
> > http://lse.sourceforge.net/locking/rclock.html.
>
> Good stuff!
>
> It would be interesting to try a filesystem benchmark such as dbench. On
> a quad PPC fget was chewing up more than its fair share of cpu time.
>
> Anton
Hello Anton,
Thank you for your suggestion. I tried dbench for on a 4-way PIII Xeon box, with
1MB L2 Cache and 1GB of RAM. I ran it on 8 GB ext2 partition with Adaptec 7896
SCSI controller. I ran "dbench 100" and "dbench 200" for five times and took the
average of the throughput and found that for
Base (2.4.2) -
100 Average Throughput = 39.628 MB/sec
200 Average Throughput = 22.792 MB/sec
Base + files_struct patch -
100 Average Throughput = 39.874 MB/sec
200 Average Throughput = 23.174 MB/sec
I found this value quite less than the one present in the README distributed
with dbench tarball. I think the numbers in the README were for a similar
machine but with 2.2.9 kernel.
As you can see the performance with files_struct patch is almost same as base.
I feel I am hitting some bottleneck other than fget() in both base and the
patched versions. I think atleast for base version I should get similar numbers
as mentions in the README for similar configuration. Though I intend to do some
profiling to look into this but it will be helpfull if you can tell me if there
is some known thing regarding this.
I am copying this to Andrew also, if he can also help. Also if you have some
dbench numbers from 2.4.x kernel, please let me have a look into those also.
Thank you,
Maneesh
--
Maneesh Soni <smaneesh@in.ibm.com>
IBM Linux Technology Center,
IBM Software Lab, Bangalore, India
next prev parent reply other threads:[~2001-04-12 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 14:43 [RFC][PATCH] Scalable FD Management using Read-Copy-Update Maneesh Soni
2001-04-12 1:29 ` Anton Blanchard
2001-04-12 15:43 ` Maneesh Soni [this message]
2001-04-12 15:51 ` [Lse-tech] " Anton Blanchard
2001-04-17 10:49 ` Scalable FD Management Maneesh Soni
2001-04-17 14:36 ` Andi Kleen
2001-04-12 18:23 ` [Lse-tech] Re: [RFC][PATCH] Scalable FD Management using Read-Copy-Update John Hawkes
2001-04-16 16:16 ` Mark Hahn
2001-04-17 9:28 ` Dipankar Sarma
2001-04-17 16:59 ` Mark Hahn
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=20010412211354.A25905@in.ibm.com \
--to=smaneesh@in.ibm.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=tridge@samba.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.