From: Cyrus Massoumi <cyrusm@gmx.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Diego Calleja <diegocg@gmail.com>,
Stephen Cuppett <cuppett@gmail.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
a.p.zijlstra@chello.nl
Subject: Re: Performance versus FreeBSD 7.0
Date: Tue, 04 Mar 2008 06:51:41 +0100 [thread overview]
Message-ID: <47CCE36D.3020000@gmx.net> (raw)
In-Reply-To: <p73y78z5r3k.fsf@bingen.suse.de>
Andi Kleen wrote:
> Cyrus Massoumi <cyrusm@gmx.net> writes:
>> IIRC, going to fine-grained file locking gave them a huge boost in
>> this particular benchmark (and maybe others).
>
> What locking? You mean their equivalent of i_mutex? There are
> already file systems on Linux that don't use it significantly
> for write.
>
>> As I said on lwn.net Peter Zijlstra posted a patch to break the global
>> file list lock about a year ago [1], but I don't think it was ever
>> merged. Here [2] are some numbers for the patchset.
>
> The file_list_lock is only for open/close which MySQL is very unlikely
> to do in its fast path. You're totally on the wrong path here I think.
Yes, Nick already corrected me, sorry for the noise :)
next prev parent reply other threads:[~2008-03-04 5:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 13:38 Performance versus FreeBSD 7.0 Stephen Cuppett
2008-02-29 14:54 ` Diego Calleja
2008-03-03 13:04 ` Nick Piggin
2008-03-03 19:02 ` Cyrus Massoumi
2008-03-03 19:24 ` Nick Piggin
2008-03-03 22:47 ` Cyrus Massoumi
2008-03-03 23:23 ` Andi Kleen
2008-03-04 5:51 ` Cyrus Massoumi [this message]
2008-03-06 12:53 ` Nick Piggin
2008-03-06 13:12 ` Andi Kleen
2008-03-03 12:34 ` Andi Kleen
2008-03-06 17:29 ` debian developer
2008-03-06 17:34 ` debian developer
[not found] <a2dDb-60y-29@gated-at.bofh.it>
[not found] ` <a2eSt-7UK-1@gated-at.bofh.it>
2009-01-25 10:07 ` Lx
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=47CCE36D.3020000@gmx.net \
--to=cyrusm@gmx.net \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=cuppett@gmail.com \
--cc=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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.