From: Rik van Riel <riel@surriel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Alexey Gladkov <legion@kernel.org>,
linux-fs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH RFC] fs,ipc: batch RCU synchronization in free_ipc
Date: Mon, 15 Aug 2022 21:05:18 -0400 [thread overview]
Message-ID: <823dd9856064cef2c7ced2cd4e9f45bf328ae6ef.camel@surriel.com> (raw)
In-Reply-To: <Yvq9SmCUX/eeUuR1@ZenIV>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
On Mon, 2022-08-15 at 22:40 +0100, Al Viro wrote:
> On Mon, Aug 15, 2022 at 05:26:20PM -0400, Rik van Riel wrote:
> > TL;DR: it runs better than it looks, and I am looking for ideas on
> > how to make it look better
>
> > Unfortunately there seems to be a tradeoff between temporarily
> > allocating things on the stack, and having slightly uglier code,
> > or adding a struct rcu_work to the struct vfsmount.
> >
> > I am not entirely happy with the way this code looks, and hoping
> > for suggestions on how to improve it.
> >
>
> IMO you are going in wrong direction with that; it's a long story,
> and I've partial writeup on that, but I won't have it ready for
> posting until the end of the week. Put it that way - there's
> a possibility of reorganizing the way mount refcounts work,
> eliminating this synchronize_rcu(). RCU delay still has to happen
> in some form, but we get smarter ways to wait for it.
>
I'm more than happy to abandon this approach.
I looked at this a bunch, and could not find a
nice way to do this the way the VFS currently
works, and am looking forward to getting this
done in a better way!
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-08-16 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 21:26 [PATCH RFC] fs,ipc: batch RCU synchronization in free_ipc Rik van Riel
2022-08-15 21:40 ` Al Viro
2022-08-16 1:05 ` Rik van Riel [this message]
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=823dd9856064cef2c7ced2cd4e9f45bf328ae6ef.camel@surriel.com \
--to=riel@surriel.com \
--cc=ebiederm@xmission.com \
--cc=kernel-team@fb.com \
--cc=legion@kernel.org \
--cc=linux-fs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox