From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@digeo.com>, Alex Tomas <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: Sun, 16 Mar 2003 00:50:45 -0800 [thread overview]
Message-ID: <20030316085045.GN1399@holomorphy.com> (raw)
In-Reply-To: <20030315220618.GY20188@holomorphy.com>
On Sat, Mar 15, 2003 at 01:51:58PM -0800, Andrew Morton wrote:
>> hm, I wonder if this should be in a separate cacheline. We may as well use a
>> single lock if they're this close together. Bill, can you test that
>> sometime?
On Sat, Mar 15, 2003 at 02:06:18PM -0800, William Lee Irwin III wrote:
> Benching now.
Sorry, this should have hit the list earlier.
Throughput 294.388 MB/sec 128 procs
dbench 128 87.22s user 4286.79s system 2984% cpu 2:26.58 total
(the "before" picture was ca. 257MB/s)
vmstat and oprofile info vanished, not sure why. A rerun is possible.
-- wli
next prev parent reply other threads:[~2003-03-16 8:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-15 21:01 [PATCH] concurrent inode allocation for ext2 against 2.5.64 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 [this message]
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
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=20030316085045.GN1399@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=bzzz@tmi.comex.ru \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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.