From: Andi Kleen <andi@firstfloor.org>
To: Frank Mayhar <fmayhar@google.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, mrubin@google.com
Subject: Re: Results of my VFS scaling evaluation.
Date: Sun, 10 Oct 2010 08:50:49 +0200 [thread overview]
Message-ID: <8739seh77a.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1286580739.3153.57.camel@bobble.smo.corp.google.com> (Frank Mayhar's message of "Fri, 08 Oct 2010 16:32:19 -0700")
Frank Mayhar <fmayhar@google.com> writes:
> Nick Piggin has been doing work on lock contention in VFS, in particular
> to remove the dcache and inode locks, and we are very interested in this
> work. He has entirely eliminated two of the most contended locks,
> replacing them with a combination of more granular locking, seqlocks,
> RCU lists and other mechanisms that reduce locking and contention in
> general. He has published this work at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git
>
> As we have run into problems with lock contention, Google is very
> interested in these improvements.
Thanks Frank for the data. Yes publication of any profiles would
be interesting. We're also seeing major issues with dcache and
inode locks in local testing.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Frank Mayhar <fmayhar@google.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, mrubin@google.com
Subject: Re: Results of my VFS scaling evaluation.
Date: Sun, 10 Oct 2010 08:50:49 +0200 [thread overview]
Message-ID: <8739seh77a.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1286580739.3153.57.camel@bobble.smo.corp.google.com> (Frank Mayhar's message of "Fri, 08 Oct 2010 16:32:19 -0700")
Frank Mayhar <fmayhar@google.com> writes:
> Nick Piggin has been doing work on lock contention in VFS, in particular
> to remove the dcache and inode locks, and we are very interested in this
> work. He has entirely eliminated two of the most contended locks,
> replacing them with a combination of more granular locking, seqlocks,
> RCU lists and other mechanisms that reduce locking and contention in
> general. He has published this work at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git
>
> As we have run into problems with lock contention, Google is very
> interested in these improvements.
Thanks Frank for the data. Yes publication of any profiles would
be interesting. We're also seeing major issues with dcache and
inode locks in local testing.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-10-10 6:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 23:32 Results of my VFS scaling evaluation Frank Mayhar
2010-10-08 23:32 ` Frank Mayhar
2010-10-09 0:33 ` Frank Mayhar
2010-10-09 0:38 ` Valerie Aurora
2010-10-09 0:38 ` Valerie Aurora
2010-10-11 18:47 ` Frank Mayhar
2010-10-11 18:47 ` Frank Mayhar
2011-01-13 11:13 ` Nick Piggin
2011-01-13 11:13 ` Nick Piggin
2010-10-09 3:16 ` Dave Chinner
2010-10-09 3:16 ` Dave Chinner
2010-10-10 6:54 ` Andi Kleen
2010-10-10 6:54 ` Andi Kleen
2010-10-10 7:37 ` Christoph Hellwig
2010-10-10 7:37 ` Christoph Hellwig
2010-10-10 8:20 ` Andi Kleen
2010-10-10 8:37 ` Christoph Hellwig
2010-10-10 8:37 ` Christoph Hellwig
2010-10-10 12:03 ` Andi Kleen
2010-10-10 12:03 ` Andi Kleen
2010-10-10 23:50 ` Dave Chinner
2010-10-10 23:31 ` Dave Chinner
2010-10-10 6:50 ` Andi Kleen [this message]
2010-10-10 6:50 ` Andi Kleen
2010-10-19 21:59 ` Results of my VFS scaling evaluation, redux Frank Mayhar
2010-10-19 21:59 ` Frank Mayhar
2010-10-19 22:03 ` Frank Mayhar
2010-10-19 22:03 ` Frank Mayhar
2010-10-22 19:03 ` VFS scaling evaluation results, redux Frank Mayhar
2010-10-22 19:03 ` Frank Mayhar
2010-10-23 0:00 ` Lin Ming
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=8739seh77a.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=fmayhar@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mrubin@google.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 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.