From: "Paul E. McKenney" <paulmck@kernel.org>
To: Rik van Riel <riel@surriel.com>
Cc: Chris Mason <clm@fb.com>, Giuseppe Scrivano <gscrivan@redhat.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH RFC fs/namespace] Make kern_unmount() use synchronize_rcu_expedited()
Date: Mon, 14 Feb 2022 13:41:19 -0800 [thread overview]
Message-ID: <20220214214119.GD4285@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20220214155536.1e0da8b6@imladris.surriel.com>
On Mon, Feb 14, 2022 at 03:55:36PM -0500, Rik van Riel wrote:
> On Mon, 14 Feb 2022 11:44:40 -0800
> "Paul E. McKenney" <paulmck@kernel.org> wrote:
> > On Mon, Feb 14, 2022 at 07:26:49PM +0000, Chris Mason wrote:
>
> > Moving from synchronize_rcu() to synchronize_rcu_expedited() does buy
> > you at least an order of magnitude. But yes, it should be possible to
> > get rid of all but one call per batch, which would be better. Maybe
> > a bit more complicated, but probably not that much.
>
> It doesn't look too bad, except for the include of ../fs/mount.h.
>
> I'm hoping somebody has a better idea on how to deal with that.
> Do we need a kern_unmount() variant that doesn't do the RCU wait,
> or should it get a parameter, or something else?
>
> Is there an ordering requirement between the synchronize_rcu call
> and zeroing out n->mq_mnt->mnt_ls?
>
> What other changes do we need to make everything right?
>
> The change below also fixes the issue that to-be-freed items that
> are queued up while the free_ipc work function runs do not result
> in the work item being enqueued again.
>
> This patch is still totally untested because the 4 year old is
> at home today :)
I agree that this should decrease grace-period latency quite a bit
more than does my patch, so here is hoping that it does work. ;-)
Thanx, Paul
> diff --git a/ipc/namespace.c b/ipc/namespace.c
> index 7bd0766ddc3b..321cbda17cfb 100644
> --- a/ipc/namespace.c
> +++ b/ipc/namespace.c
> @@ -17,6 +17,7 @@
> #include <linux/proc_ns.h>
> #include <linux/sched/task.h>
>
> +#include "../fs/mount.h"
> #include "util.h"
>
> static struct ucounts *inc_ipc_namespaces(struct user_namespace *ns)
> @@ -117,10 +118,7 @@ void free_ipcs(struct ipc_namespace *ns, struct ipc_ids *ids,
>
> static void free_ipc_ns(struct ipc_namespace *ns)
> {
> - /* mq_put_mnt() waits for a grace period as kern_unmount()
> - * uses synchronize_rcu().
> - */
> - mq_put_mnt(ns);
> + mntput(ns->mq_mnt);
> sem_exit_ns(ns);
> msg_exit_ns(ns);
> shm_exit_ns(ns);
> @@ -134,11 +132,19 @@ static void free_ipc_ns(struct ipc_namespace *ns)
> static LLIST_HEAD(free_ipc_list);
> static void free_ipc(struct work_struct *unused)
> {
> - struct llist_node *node = llist_del_all(&free_ipc_list);
> + struct llist_node *node;
> struct ipc_namespace *n, *t;
>
> - llist_for_each_entry_safe(n, t, node, mnt_llist)
> - free_ipc_ns(n);
> + while ((node = llist_del_all(&free_ipc_list))) {
> + llist_for_each_entry(n, node, mnt_llist)
> + real_mount(n->mq_mnt)->mnt_ns = NULL;
> +
> + /* Wait for the last users to have gone away. */
> + synchronize_rcu();
> +
> + llist_for_each_entry_safe(n, t, node, mnt_llist)
> + free_ipc_ns(n);
> + }
> }
>
> /*
>
next prev parent reply other threads:[~2022-02-14 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 19:05 Paul E. McKenney
2022-02-14 19:26 ` Chris Mason
2022-02-14 19:44 ` Paul E. McKenney
2022-02-14 20:55 ` Rik van Riel
2022-02-14 21:41 ` Paul E. McKenney [this message]
2022-02-15 18:28 ` Chris Mason
2022-04-26 6:59 ` Christoph Bartoschek
2022-04-26 14:09 ` Paul E. McKenney
2022-04-26 22:58 ` Christoph Bartoschek
2022-04-26 23:11 ` Paul E. McKenney
2022-04-27 12:19 ` Chris Mason
2022-04-27 15:01 ` Paul E. McKenney
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=20220214214119.GD4285@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=Kernel-team@fb.com \
--cc=clm@fb.com \
--cc=gscrivan@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.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®