All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:22:28 -0800	[thread overview]
Message-ID: <227420000.1047676948@flay> (raw)
In-Reply-To: <m3zno3grfz.fsf@lexa.home.net>

SDET on my machine (16x NUMA-Q) has fallen in love with your patch, 
and has decided to elope with it to a small desert island. This is 
despite it's one disk hung off node 0, and the IO througput of a 
slightly damp piece of cotton thread. Apologies for the loss of your 
patch as it gets whisked away ;-)

M.

PS. Oh, I had this bit, per akpm-instructions: For best results, add ____cacheline_aligned_in_smp to struct ext2_bg_info

PPS. I'll try to run some more focused tests with aim7 over the weekend.
As if we needed it ...

-------------------------

DISCLAIMER: SPEC(tm) and the benchmark name SDET(tm) are registered
trademarks of the Standard Performance Evaluation Corporation. This 
benchmarking was performed for research purposes only, and the run results
are non-compliant and not-comparable with any published results.

Results are shown as percentages of the first set displayed

SDET 1  (see disclaimer)
                           Throughput    Std. Dev
          2.5.64-bk3-mjb3       100.0%         1.8%
         2.5.64-mjb3-ext2       102.0%         1.1%

SDET 2  (see disclaimer)
                           Throughput    Std. Dev
          2.5.64-bk3-mjb3       100.0%         3.7%
         2.5.64-mjb3-ext2       106.1%         3.1%

SDET 4  (see disclaimer)
                           Throughput    Std. Dev
          2.5.64-bk3-mjb3       100.0%         1.5%
         2.5.64-mjb3-ext2       101.1%         2.1%

SDET 8  (see disclaimer)
                           Throughput    Std. Dev
          2.5.64-bk3-mjb3       100.0%         0.2%
         2.5.64-mjb3-ext2       113.3%         0.7%

SDET 16  (see disclaimer)
                           Throughput    Std. Dev
          2.5.64-bk3-mjb3       100.0%         1.1%
         2.5.64-mjb3-ext2       167.1%         0.8%

SDET 32  (see disclaimer)
                           Throughput    Std. Dev
          2.5.64-bk3-mjb3       100.0%         0.9%
         2.5.64-mjb3-ext2       170.7%         0.1%

SDET 64  (see disclaimer)
                           Throughput    Std. Dev
          2.5.64-bk3-mjb3       100.0%         0.7%
         2.5.64-mjb3-ext2       157.2%         0.5%

SDET 128  (see disclaimer)
                           Throughput    Std. Dev
          2.5.64-bk3-mjb3       100.0%         0.3%
         2.5.64-mjb3-ext2       151.3%         0.8%


  parent reply	other threads:[~2003-03-14 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 15:41 [PATCH] concurrent block allocation for ext3 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 [this message]
2003-03-15  2:56   ` Martin J. Bligh
2003-03-15  6:08     ` 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=227420000.1047676948@flay \
    --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 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.