All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@kernel.dk>
To: Nick Piggin <npiggin@kernel.dk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] fs: scale vfsmount refcount (was Re: rcu-walk and dcache scaling tree update and status)
Date: Mon, 13 Dec 2010 14:43:22 +1100	[thread overview]
Message-ID: <20101213034322.GA7975@amd> (raw)
In-Reply-To: <20101213033110.GA7898@amd>

On Mon, Dec 13, 2010 at 02:31:10PM +1100, Nick Piggin wrote:
> (Yes this little bouncing atomic hurts, badly, even on my small 2s12c
> tightly connected system on the parallel git diff workload -- because
> there are other bouncing kernel cachelines in this workload).
          ^^^
      are no other


  reply	other threads:[~2010-12-13  3:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13  2:37 rcu-walk and dcache scaling tree update and status Nick Piggin
2010-12-13  2:42 ` [patch] fs: scale vfsmount refcount (was Re: rcu-walk and dcache scaling tree update and status) Nick Piggin
2010-12-13  3:31   ` Nick Piggin
2010-12-13  3:43     ` Nick Piggin [this message]
2010-12-13  7:25   ` Eric Dumazet
2010-12-13  8:33     ` Nick Piggin
2010-12-14 12:40     ` Nick Piggin
2010-12-15  8:16       ` Andreas Dilger
2010-12-15 10:24         ` Nick Piggin
2010-12-13  2:53 ` rcu-walk and dcache scaling tree update and status Ed Tomlinson
2010-12-13  2:59   ` Nick Piggin
2010-12-13  3:45     ` Stephen Rothwell
2010-12-13  3:50       ` Nick Piggin
2010-12-13  3:40 ` Stephen Rothwell
2010-12-13  3:48   ` Nick Piggin
2010-12-14  0:03     ` Stephen Rothwell
2010-12-14  0:16       ` Stephen Rothwell

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=20101213034322.GA7975@amd \
    --to=npiggin@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --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 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.