From: Eric Dumazet <eric.dumazet@gmail.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Frank Mayhar <fmayhar@google.com>,
John Stultz <johnstul@us.ibm.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [patch 2/4] lglock: introduce special lglock and brlock spin locks
Date: Fri, 04 Jun 2010 16:24:25 +0200 [thread overview]
Message-ID: <1275661465.2482.174.camel@edumazet-laptop> (raw)
In-Reply-To: <20100604141318.GC26335@laptop>
Le samedi 05 juin 2010 à 00:13 +1000, Nick Piggin a écrit :
> On Fri, Jun 04, 2010 at 09:56:03AM +0200, Eric Dumazet wrote:
> > IMHO some changes in Documentation/ would be needed
>
> I wonder where, and what?
>
>
Documentation/memory-barriers.txt (around line 1111)
Documentation/spinlocks.txt (change its name ?)
Section 1 : spinlocks
Section 2 : rwlocks
Section 3 : lglock/brlock ?
next prev parent reply other threads:[~2010-06-04 14:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 6:43 [patch 0/4] Initial vfs scalability patches again Nick Piggin
2010-06-04 6:43 ` [patch 1/4] fs: cleanup files_lock Nick Piggin
2010-06-04 8:38 ` Christoph Hellwig
2010-06-04 14:20 ` Nick Piggin
2010-06-04 14:39 ` Andi Kleen
2010-06-04 15:10 ` Christoph Hellwig
2010-06-04 18:39 ` [PATCH, RFC] tty: stop abusing file->f_u.fu_list Christoph Hellwig
2010-06-04 19:35 ` Al Viro
2010-06-05 11:39 ` Nick Piggin
2010-06-08 5:22 ` Nick Piggin
2010-06-04 6:43 ` [patch 2/4] lglock: introduce special lglock and brlock spin locks Nick Piggin
2010-06-04 7:56 ` Eric Dumazet
2010-06-04 14:13 ` Nick Piggin
2010-06-04 14:24 ` Eric Dumazet [this message]
2010-06-04 15:03 ` Paul E. McKenney
2010-06-04 15:12 ` Nick Piggin
2010-06-04 6:43 ` [patch 3/4] fs: scale files_lock Nick Piggin
2010-06-04 6:43 ` [patch 4/4] fs: brlock vfsmount_lock Nick Piggin
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=1275661465.2482.174.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=ak@linux.intel.com \
--cc=fmayhar@google.com \
--cc=johnstul@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=viro@ZenIV.linux.org.uk \
/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®