From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Alex Tomas <bzzz@tmi.comex.ru>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>, anton@samba.org
Subject: Re: [PATCH] concurrent block allocation for ext3
Date: Fri, 14 Mar 2003 22:08:24 -0800 [thread overview]
Message-ID: <4110000.1047708504@[10.10.2.4]> (raw)
In-Reply-To: <251250000.1047696997@flay>
> before:
> Throughput 48.5304 MB/sec (NB=60.663 MB/sec 485.304 MBit/sec) 256 procs
> after:
> Throughput 58.8483 MB/sec (NB=73.5603 MB/sec 588.483 MBit/sec) 256 procs
OK, akpm wanted dbench 32 instead:
before:
Throughput 187.637 MB/sec (NB=234.546 MB/sec 1876.37 MBit/sec) 32 procs
after:
Throughput 378.664 MB/sec (NB=473.33 MB/sec 3786.64 MBit/sec) 32 procs
/me likes.
M.
prev parent reply other threads:[~2003-03-15 5:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 15:41 Alex Tomas
2003-03-10 16:25 ` Andreas Dilger
2003-03-10 16:33 ` Alex Tomas
2003-03-10 16:43 ` Daniel Phillips
2003-03-14 21:22 ` Martin J. Bligh
2003-03-15 2:56 ` Martin J. Bligh
2003-03-15 6:08 ` Martin J. Bligh [this message]
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='4110000.1047708504@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=anton@samba.org \
--cc=bzzz@tmi.comex.ru \
--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 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®