public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@linuxcare.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] pagecache SMP-scalability patch [was: spinlock usage]
Date: Wed, 21 Mar 2001 23:27:02 +1100	[thread overview]
Message-ID: <20010321232701.A16455@linuxcare.com> (raw)
In-Reply-To: <20010321180607.A11941@linuxcare.com> <Pine.LNX.4.30.0103211301530.5270-100000@elte.hu>
In-Reply-To: <Pine.LNX.4.30.0103211301530.5270-100000@elte.hu>; from mingo@elte.hu on Wed, Mar 21, 2001 at 01:11:35PM +0100

 
Hi,

>   http://people.redhat.com/~mingo/smp-pagecache-patches/pagecache-2.4.2-H1
> 
> this patch splits up the main scalability offender in non-RAM-limited
> dbench runs, which is pagecache_lock. The patch was designed and written
> by David Miller, and is being forward ported / maintained by me. (The new
> pagecache lock design is similar to TCP's hashed spinlocks, which proved
> to scale excellently.)

Thanks Ingo! Davem told me about this a while ago but I had forgotten
about it. I'll do some runs tomorrow including ones which dont fit in
RAM.

> (about lstat(): IMO lstat() should not call into the lowlevel FS code.)

Ooops, sorry I meant stats as in statistics :)

Anton

  reply	other threads:[~2001-03-21 12:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21  7:06 spinlock usage - ext2_get_block, lru_list_lock Anton Blanchard
2001-03-21  8:46 ` Andreas Dilger
2001-03-21  9:05   ` Mitchell Blank Jr
2001-03-21  9:41     ` Andreas Dilger
2001-03-21 12:11 ` [patch] pagecache SMP-scalability patch [was: spinlock usage] Ingo Molnar
2001-03-21 12:27   ` Anton Blanchard [this message]
2001-03-21 12:54   ` Alexander Viro
2001-03-21 12:59     ` Ingo Molnar
2001-03-21 13:56       ` Alexander Viro
2001-03-21 14:01         ` Ingo Molnar
2001-03-21 16:52 ` spinlock usage - ext2_get_block, lru_list_lock Linus Torvalds
2001-03-21 17:16   ` Alexander Viro
2001-03-21 18:15     ` James Lewis Nance
2001-03-21 21:01       ` Alexander Viro

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=20010321232701.A16455@linuxcare.com \
    --to=anton@linuxcare.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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