From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
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,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [RFC, PATCH] CLONE_NEWIPC and exit_group()
Date: Tue, 26 Jun 2012 20:45:42 +0300 [thread overview]
Message-ID: <20120626174542.GA15482@otc-wbsnb-06> (raw)
In-Reply-To: <20120626170457.GA31175@mail.hallyn.com>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
On Tue, Jun 26, 2012 at 05:04:57PM +0000, Serge E. Hallyn wrote:
> Quoting Kirill A. Shutemov (kirill.shutemov@linux.intel.com):
> > Hi,
> >
> > Patch to move kern_unmount() out of exit_group() code path is below.
> > Dmitry, could you check if it's beneficial for your use-case?
>
> Hi,
>
> sorry, I don't seem to have the thread handy for contest. What is the
> point of this? The work being moved was not being done under lock,
> so what is this meant to gain?
It's basically addition to this patch (tested with the patch applied):
http://thread.gmane.org/gmane.linux.kernel.cifs/6347/focus=23929
Some context: Dmitry has workload which run a lot of short-living tasks in
sandboxed environment. He noticed that exit_group() syscall of the last
process in IPC namespace is a bottleneck.
The bottleneck was mainly due rcu_barrier() in kern_umount(). It's fixed
by patch in the link (Andrew took it in -mm).
But probably having kern_umount() in exit_group() code path is not a good
idea from scalability point of view?..
--
Kirill A. Shutemov
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-26 17:44 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 [this message]
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
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=20120626174542.GA15482@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=serge@hallyn.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®