From: Giuseppe Scrivano <gscrivan@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
mingo@kernel.org, dave@stgolabs.net
Subject: Re: [RFC PATCH] ipc, mqueue: lazy call kern_mount_data in new namespaces
Date: Wed, 29 Nov 2017 11:33:28 +0100 [thread overview]
Message-ID: <87wp29l6h3.fsf@redhat.com> (raw)
In-Reply-To: <20171128135316.6d7bba7fe909ba3d90e318db@linux-foundation.org> (Andrew Morton's message of "Tue, 28 Nov 2017 13:53:16 -0800")
Andrew Morton <akpm@linux-foundation.org> writes:
> OK, but this simply moves the expense so it happens later on. Why is
> that better?
the optimization is for new IPC namespaces that don't use mq_open. In
this case there won't be any kern_mount_data cost at all.
Regards,
Giuseppe
next prev parent reply other threads:[~2017-11-29 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 12:55 [RFC PATCH] ipc, mqueue: lazy call kern_mount_data in new namespaces Giuseppe Scrivano
2017-11-28 7:09 ` Davidlohr Bueso
2017-11-28 21:53 ` Andrew Morton
2017-11-29 10:33 ` Giuseppe Scrivano [this message]
2017-11-29 22:17 ` Andrew Morton
2017-11-30 12:20 ` Giuseppe Scrivano
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=87wp29l6h3.fsf@redhat.com \
--to=gscrivan@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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;
as well as URLs for NNTP newsgroup(s).