From: Andrew Morton <akpm@digeo.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: bzzz@tmi.comex.ru, linux-kernel@vger.kernel.org,
ext2-devel@lists.sourceforge.net
Subject: Re: [PATCH] concurrent inode allocation for ext2 against 2.5.64
Date: Sat, 15 Mar 2003 14:37:18 -0800 [thread overview]
Message-ID: <20030315143718.60e006b7.akpm@digeo.com> (raw)
In-Reply-To: <20030315220241.GX20188@holomorphy.com>
William Lee Irwin III <wli@holomorphy.com> wrote:
>
> On Sun, Mar 16, 2003 at 12:01:38AM +0300, Alex Tomas wrote:
> > here is the patch for ext2 concurrent inode allocation. should be applied
> > on top of previous concurrent-balloc patch. tested on dual p3 for several
> > hours of stress-test + fsck. hope someone test it on big iron ;)
>
> 32x/48GB NUMA-Q
>
> Throughput 257.986 MB/sec 128 procs
> dbench 128 95.36s user 4833.06s system 2832% cpu 2:53.97 total
>
> vma samples %-age symbol name
> c01dc9ac 4532033 21.4566 .text.lock.dec_and_lock
> c0169c0b 3835802 18.1603 .text.lock.dcache
> c0106ff4 1741849 8.24666 default_idle
Looks like it's gone nuts when 128 processes all try to close lots of
files at the same time.
One possible reason for this leaping out is that all the instances are now
achieving more uniform runtimes. You can tell that by comparing the dbench
dots.
next prev parent reply other threads:[~2003-03-15 22:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-15 21:01 Alex Tomas
2003-03-15 21:17 ` William Lee Irwin III
2003-03-15 21:51 ` Andrew Morton
2003-03-15 22:06 ` William Lee Irwin III
2003-03-16 8:50 ` William Lee Irwin III
2003-03-15 22:02 ` William Lee Irwin III
2003-03-15 22:23 ` William Lee Irwin III
2003-03-15 22:37 ` Andrew Morton [this message]
2003-03-15 22:58 ` William Lee Irwin III
2003-03-15 23:08 ` William Lee Irwin III
2003-03-15 23:18 ` William Lee Irwin III
2003-03-15 23:40 ` William Lee Irwin III
2003-03-16 8:25 ` Martin J. Bligh
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=20030315143718.60e006b7.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=bzzz@tmi.comex.ru \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®