From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Doug Ledford <dledford@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Serge Hallyn <serge.hallyn@canonical.com>,
linux-kernel@vger.kernel.org,
"Dmitry V. Levin" <ldv@altlinux.org>,
Pavel Emelyanov <xemul@openvz.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [RFC, PATCH] CLONE_NEWIPC and exit_group()
Date: Thu, 12 Jul 2012 18:07:02 +0300 [thread overview]
Message-ID: <20120712150702.GA1897@otc-wbsnb-06> (raw)
In-Reply-To: <20120711152422.a1f07bd5.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 2685 bytes --]
On Wed, Jul 11, 2012 at 03:24:22PM -0700, Andrew Morton wrote:
> Am I reading that right? 1000 forks take 33 seconds, with basically
> all of it just sitting there asleep? This look quite terrible - what
> causes this?
It seems free_nsproxy() + synchronize_rcu() are too heavy to be in
exit_group() path. Patch below helps: 8s -> ~0.5s for me.
I'll prepare cleaner patch later if the approach is good enough.
Also, I noticed that put_nsproxy() calls free_nsproxy() without
synchronize_rcu(). It looks wrong.
diff --git a/include/linux/nsproxy.h b/include/linux/nsproxy.h
index cc37a55..1d26be7 100644
--- a/include/linux/nsproxy.h
+++ b/include/linux/nsproxy.h
@@ -24,6 +24,7 @@ struct fs_struct;
*/
struct nsproxy {
atomic_t count;
+ struct work_struct free_nsproxy_work;
struct uts_namespace *uts_ns;
struct ipc_namespace *ipc_ns;
struct mnt_namespace *mnt_ns;
diff --git a/kernel/nsproxy.c b/kernel/nsproxy.c
index b576f7f..63618cc 100644
--- a/kernel/nsproxy.c
+++ b/kernel/nsproxy.c
@@ -41,13 +41,17 @@ struct nsproxy init_nsproxy = {
#endif
};
+static void free_nsproxy_synced(struct work_struct *work);
+
static inline struct nsproxy *create_nsproxy(void)
{
struct nsproxy *nsproxy;
nsproxy = kmem_cache_alloc(nsproxy_cachep, GFP_KERNEL);
- if (nsproxy)
+ if (nsproxy) {
atomic_set(&nsproxy->count, 1);
+ INIT_WORK(&nsproxy->free_nsproxy_work, free_nsproxy_synced);
+ }
return nsproxy;
}
@@ -178,6 +182,23 @@ void free_nsproxy(struct nsproxy *ns)
kmem_cache_free(nsproxy_cachep, ns);
}
+static void free_nsproxy_synced(struct work_struct *work)
+{
+ struct nsproxy *ns = container_of(work, struct nsproxy,
+ free_nsproxy_work);
+
+ /*
+ * wait for others to get what they want from this nsproxy.
+ *
+ * cannot release this nsproxy via the call_rcu() since
+ * put_mnt_ns() will want to sleep
+ */
+ synchronize_rcu();
+
+ free_nsproxy(ns);
+}
+
+
/*
* Called from unshare. Unshare all the namespaces part of nsproxy.
* On success, returns the new nsproxy.
@@ -215,16 +236,8 @@ void switch_task_namespaces(struct task_struct *p, struct nsproxy *new)
rcu_assign_pointer(p->nsproxy, new);
- if (ns && atomic_dec_and_test(&ns->count)) {
- /*
- * wait for others to get what they want from this nsproxy.
- *
- * cannot release this nsproxy via the call_rcu() since
- * put_mnt_ns() will want to sleep
- */
- synchronize_rcu();
- free_nsproxy(ns);
- }
+ if (ns && atomic_dec_and_test(&ns->count))
+ schedule_work(&ns->free_nsproxy_work);
}
void exit_task_namespaces(struct task_struct *p)
--
Kirill A. Shutemov
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-12 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 12:04 Kirill A. Shutemov
2012-06-26 17:04 ` Serge E. Hallyn
2012-06-26 17:45 ` Kirill A. Shutemov
2012-06-26 17:55 ` Serge E. Hallyn
2012-06-27 12:34 ` Dmitry V. Levin
2012-06-27 13:01 ` Serge Hallyn
2012-07-10 8:50 ` Kirill A. Shutemov
2012-07-11 22:24 ` Andrew Morton
2012-07-12 15:07 ` Kirill A. Shutemov [this message]
2012-07-12 18:54 ` Serge Hallyn
2012-07-12 19:06 ` Doug Ledford
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=20120712150702.GA1897@otc-wbsnb-06 \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dledford@redhat.com \
--cc=kirill@shutemov.name \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@canonical.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@openvz.org \
/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
Powered by JetHome