From: Daniel Phillips <phillips@bonn-fries.net>
To: Andrew Morton <akpm@zip.com.au>, Yusuf Goolamabbas <yusufg@outblaze.com>
Cc: ext3-users@redhat.com, linux-kernel@vger.kernel.org,
anton@samba.org, axboe@suse.de
Subject: Re: 2.4.17-pre2+ext3-0.9.16+anton's cache aligned smp
Date: Fri, 7 Dec 2001 16:27:27 +0100 [thread overview]
Message-ID: <E16CMuT-0000tz-00@starship.berlin> (raw)
In-Reply-To: <3C0B12C5.F8F05016@zip.com.au> <20011206163056.A15550@outblaze.com> <3C0F301D.3368595@zip.com.au>
In-Reply-To: <3C0F301D.3368595@zip.com.au>
On December 6, 2001 09:45 am, Andrew Morton wrote:
> Yusuf Goolamabbas wrote:
> >
> > Running 2.4.17-pre2 + ext3-0.9.16 + Anton Blanchards
> > cacheline_aligned_smp patch available at
> >
> > http://samba.org/~anton/linux/cacheline_aligned/
>
> omigod look at that graph.
>
> Excuse me while I get frustrated. Will someone *please* send that
> damn patch to marcelo@conectiva.com.br?
>
> (It can be improved further by putting padding *behind* the lock
> but hey).
>
> > ...
> >
> > With Anton's patch, the number of ctx-swtch/sec drops by around 3000
> > from avg of 9000 (for 17-pre2+ext3) to avg of 6000 (with anton) as seen
> > by vmstat 1
>
> Really? The spinlock cacheline alignment alone made that
> difference? I wonder why.
Before getting *too* excited, remember, it's dbench, so effects could easily
be magnified. Maybe test with something better behaved?
--
Daniel
prev parent reply other threads:[~2001-12-07 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 5:51 ext3-0.9.16 against linux-2.4.17-pre2 Andrew Morton
2001-12-05 12:32 ` Florian Lohoff
2001-12-05 12:36 ` Mike Fedyk
2001-12-05 12:37 ` Florian Lohoff
2001-12-05 23:42 ` Robert Love
2001-12-06 8:30 ` 2.4.17-pre2+ext3-0.9.16+anton's cache aligned smp Yusuf Goolamabbas
2001-12-06 8:39 ` Jens Axboe
2001-12-06 8:45 ` Andrew Morton
2001-12-06 13:02 ` Anton Blanchard
2001-12-07 15:27 ` Daniel Phillips [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=E16CMuT-0000tz-00@starship.berlin \
--to=phillips@bonn-fries.net \
--cc=akpm@zip.com.au \
--cc=anton@samba.org \
--cc=axboe@suse.de \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yusufg@outblaze.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®