From: Nick Piggin <npiggin@kernel.dk>
To: Ed Tomlinson <edt@aei.ca>
Cc: Nick Piggin <npiggin@kernel.dk>,
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: rcu-walk and dcache scaling tree update and status
Date: Mon, 13 Dec 2010 13:59:10 +1100 [thread overview]
Message-ID: <20101213025910.GA6981@amd> (raw)
In-Reply-To: <201012122153.33427.edt@aei.ca>
On Sun, Dec 12, 2010 at 09:53:32PM -0500, Ed Tomlinson wrote:
> On Sunday 12 December 2010 21:37:33 Nick Piggin wrote:
> > Final note:
> > You won't be able to reproduce the parallel path walk scalability
> > numbers that I've posted, because the vfsmount refcounting scalability
> > patch is not included. I have a new idea for that now, so I'll be asking
> > for comments with that soon.
>
> I get this when building:
>
> security/security.c: In function 'security_inode_exec_permission':
> security/security.c:520: error: 'rcu' undeclared (first use in this function)
> security/security.c:520: error: (Each undeclared identifier is reported only once
> security/security.c:520: error: for each function it appears in.)
> make[1]: *** [security/security.o] Error 1
> make: *** [security] Error 2
>
> Missing include maybe?
Ah, missed permutation while doing a final build check. `rcu` should
just be renamed to `flags`.
next prev parent reply other threads:[~2010-12-13 2:59 UTC|newest]
Thread overview: 20+ 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
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2010-12-13 2:37 Nick Piggin
2010-12-13 16:48 Sedat Dilek
2010-12-13 23:21 ` 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=20101213025910.GA6981@amd \
--to=npiggin@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=edt@aei.ca \
--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.