public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Maneesh Soni <smaneesh@in.ibm.com>
Cc: lse tech <lse-tech@lists.sourceforge.net>,
	lkml <linux-kernel@vger.kernel.org>,
	Paul.McKenney@us.ibm.com, ak@suse.de, hawkes@engr.sgi.com,
	dipankar@sequent.com
Subject: Re: [RFC][PATCH] Scalable FD Management using Read-Copy-Update
Date: Wed, 11 Apr 2001 18:29:30 -0700	[thread overview]
Message-ID: <20010411182929.A16665@va.samba.org> (raw)
In-Reply-To: <20010409201311.D9013@in.ibm.com>
In-Reply-To: <20010409201311.D9013@in.ibm.com>; from smaneesh@in.ibm.com on Mon, Apr 09, 2001 at 08:13:11PM +0530


> 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

  reply	other threads:[~2001-04-12  1:32 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 [this message]
2001-04-12 15:43   ` [Lse-tech] " Maneesh Soni
2001-04-12 15:51     ` 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=20010411182929.A16665@va.samba.org \
    --to=anton@samba.org \
    --cc=Paul.McKenney@us.ibm.com \
    --cc=ak@suse.de \
    --cc=dipankar@sequent.com \
    --cc=hawkes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=smaneesh@in.ibm.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