From: Nathan Zimmer <nzimmer@sgi.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<adobriyan@gmail.com>, Alexander Viro <viro@zeniv.linux.org.uk>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] fs/proc: Move kfree outside pde_unload_lock
Date: Thu, 23 Aug 2012 12:54:56 -0500 [thread overview]
Message-ID: <50366E70.1020109@sgi.com> (raw)
In-Reply-To: <1345671778.5158.2369.camel@edumazet-glaptop>
On 08/22/2012 04:42 PM, Eric Dumazet wrote:
> On Wed, 2012-08-22 at 20:28 +0200, Eric Dumazet wrote:
>
>> Thats interesting, but if you really want this to fly, one RCU
>> conversion would be much better ;)
>>
>> pde_users would be an atomic_t and you would avoid the spinlock
>> contention.
> Here is what I had in mind, I would be interested to know how it helps a 512 core machine ;)
>
Thanks, I knew if I just took my time and read the rcu documentation
thoroughly that the answer would be forthcoming. ;)
Unfortunately I have to wait till tomorrow to get big box and test it.
next prev parent reply other threads:[~2012-08-23 17:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 16:38 [PATCH] fs/proc: Move kfree outside pde_unload_lock Nathan Zimmer
2012-08-22 16:38 ` [PATCH] fs/prof: Update comment on pde_unload_lock Nathan Zimmer
2012-08-22 18:28 ` [PATCH] fs/proc: Move kfree outside pde_unload_lock Eric Dumazet
2012-08-22 21:42 ` Eric Dumazet
2012-08-23 17:54 ` Nathan Zimmer [this message]
2012-08-24 14:48 ` Nathan Zimmer
2012-08-24 14:58 ` Eric Dumazet
2012-08-24 16:45 ` Nathan Zimmer
2012-08-24 21:43 ` Nathan Zimmer
2012-08-28 20:38 ` Alexey Dobriyan
2012-08-29 4:11 ` Eric Dumazet
2012-08-29 8:32 ` Alexey Dobriyan
2012-08-29 13:50 ` Alexey Dobriyan
2012-08-29 14:24 ` Eric Dumazet
2012-09-17 15:57 ` Nathan Zimmer
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=50366E70.1020109@sgi.com \
--to=nzimmer@sgi.com \
--cc=adobriyan@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.