linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: lsf10-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org
Subject: [ATTEND] LSF10 proposal: vfs scalability
Date: Tue, 9 Mar 2010 21:19:55 +1100	[thread overview]
Message-ID: <20100309101955.GF8653@laptop> (raw)

Hi, I would like to attend LSF10 to discuss VFS scalability improvements.

VFS scalability is about removing global locks from the VFS,
dcache_lock, inode_lock, etc. which basically stand in the way of making
fs operations to any filesystem and pseudo filesystem "scalable". I do
hope to have made some progress towards merging pieces by the time of
LSF10, but it won't be complete.

I think everybody is agreed that the global VFS locks are going to run
out of steam sooner or later (now at 32 threads per socket and no sign
of slowing down). Some real users are already hitting problems (eg. see:
google's batched iput/dput patches). The questions will just be HOW to
improve scalability and how far to go.

I have proposed some approaches for improving scalability. These changes
need careful reviews from filesystems and VFS maintainers. So I think
LSF would be a good place to discuss this. Perhaps even look at specific
difficult patches.

Thanks,
Nick


                 reply	other threads:[~2010-03-09 10:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100309101955.GF8653@laptop \
    --to=npiggin@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf10-pc@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).