From: "Stephen C. Tweedie" <sct@redhat.com>
To: Juergen Doelle <jdoelle@de.ibm.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org, Mark Hemment <markhe@veritas.com>,
lse-tech@lists.sourceforge.net, Steve Fox <stevefx@us.ibm.com>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: [PATCH] Align VM locks, new spinlock patch
Date: Mon, 24 Sep 2001 15:02:59 +0100 [thread overview]
Message-ID: <20010924150259.A13817@redhat.com> (raw)
In-Reply-To: <3BAB3D65.2FDD170C@de.ibm.com>
In-Reply-To: <3BAB3D65.2FDD170C@de.ibm.com>; from jdoelle@de.ibm.com on Fri, Sep 21, 2001 at 03:15:17PM +0200
Hi,
On Fri, Sep 21, 2001 at 03:15:17PM +0200, Juergen Doelle wrote:
> 2.4.10 2.4.10 + improvement
> spinlock patch by patch
>
> U 103.77 102.14 - 1.6%
> 1 96.82 96.77 - 0.1%
> 2 155.32 155.62 0.2%
> 4 209.45 222.11 6.0%
> 8 208.06 234.82 12.9%
>
> The improvement is less than in previous posted results, because the
> pagemap_lru_lock and the lru_list_lock are already cacheline aligned
> in 2.4.10 (2.4.9).
Do you have CPU utilisation differences for these cases, as well as
pure IO bandwidth differences? It would be interesting to see just
how much the IO code's internal latency impacts on the final dbench
numbers.
--Stephen
next prev parent reply other threads:[~2001-09-24 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 13:15 [PATCH] Align VM locks, new spinlock patch Juergen Doelle
2001-09-22 23:07 ` Andrew Morton
2001-09-24 14:02 ` Stephen C. Tweedie [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-26 15:15 Juergen Doelle
2001-09-26 15:15 Juergen Doelle
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=20010924150259.A13817@redhat.com \
--to=sct@redhat.com \
--cc=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=jdoelle@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=markhe@veritas.com \
--cc=stevefx@us.ibm.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