From: Jeff Layton <jlayton@kernel.org>
To: Christian Brauner <brauner@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Amir Goldstein <amir73il@gmail.com>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH] uidgid: make sure we fit into one cacheline
Date: Tue, 10 Sep 2024 09:51:37 -0400 [thread overview]
Message-ID: <80c0e982a5a55f6c0a0eeb4e717b9fc32d93de3f.camel@kernel.org> (raw)
In-Reply-To: <20240910-work-uid_gid_map-v1-1-e6bc761363ed@kernel.org>
On Tue, 2024-09-10 at 10:16 +0200, Christian Brauner wrote:
> When I expanded uidgid mappings I intended for a struct uid_gid_map to
> fit into a single cacheline on x86 as they tend to be pretty
> performance sensitive (idmapped mounts etc). But a 4 byte hole was added
> that brought it over 64 bytes. Fix that by adding the static extent
> array and the extent counter into a substruct. C's type punning for
> unions guarantees that we can access ->nr_extents even if the last
> written to member wasn't within the same object. This is also what we
> rely on in struct_group() and friends. This of course relies on
> non-strict aliasing which we don't do.
>
> 99) If the member used to read the contents of a union object is not the
> same as the member last used to store a value in the object, the
> appropriate part of the object representation of the value is
> reinterpreted as an object representation in the new type as
> described in 6.2.6 (a process sometimes called "type punning").
>
> Link: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2310.pdf
> Signed-off-by: Christian Brauner <brauner@kernel.org>
> ---
> Before:
>
> struct uid_gid_map {
> u32 nr_extents; /* 0 4 */
>
> /* XXX 4 bytes hole, try to pack */
>
> union {
> struct uid_gid_extent extent[5]; /* 8 60 */
> struct {
> struct uid_gid_extent * forward; /* 8 8 */
> struct uid_gid_extent * reverse; /* 16 8 */
> }; /* 8 16 */
> }; /* 8 64 */
>
> /* size: 72, cachelines: 2, members: 2 */
> /* sum members: 68, holes: 1, sum holes: 4 */
> /* last cacheline: 8 bytes */
> };
>
> After:
>
> struct uid_gid_map {
> union {
> struct {
> struct uid_gid_extent extent[5]; /* 0 60 */
> u32 nr_extents; /* 60 4 */
> }; /* 0 64 */
> struct {
> struct uid_gid_extent * forward; /* 0 8 */
> struct uid_gid_extent * reverse; /* 8 8 */
> }; /* 0 16 */
> }; /* 0 64 */
>
> /* size: 64, cachelines: 1, members: 1 */
> };
> ---
> include/linux/user_namespace.h | 6 ++++--
> kernel/user.c | 6 +++---
> 2 files changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/user_namespace.h b/include/linux/user_namespace.h
> index 6030a8235617..3625096d5f85 100644
> --- a/include/linux/user_namespace.h
> +++ b/include/linux/user_namespace.h
> @@ -21,9 +21,11 @@ struct uid_gid_extent {
> };
>
> struct uid_gid_map { /* 64 bytes -- 1 cache line */
> - u32 nr_extents;
> union {
> - struct uid_gid_extent extent[UID_GID_MAP_MAX_BASE_EXTENTS];
> + struct {
> + struct uid_gid_extent extent[UID_GID_MAP_MAX_BASE_EXTENTS];
> + u32 nr_extents;
> + };
Is this any different from just moving nr_extents to the end of
struct_uid_gid_map? I don't quite get how moving it into the union
improves things.
> struct {
> struct uid_gid_extent *forward;
> struct uid_gid_extent *reverse;
> diff --git a/kernel/user.c b/kernel/user.c
> index aa1162deafe4..f46b1d41163b 100644
> --- a/kernel/user.c
> +++ b/kernel/user.c
> @@ -36,33 +36,33 @@ EXPORT_SYMBOL_GPL(init_binfmt_misc);
> */
> struct user_namespace init_user_ns = {
> .uid_map = {
> - .nr_extents = 1,
> {
> .extent[0] = {
> .first = 0,
> .lower_first = 0,
> .count = 4294967295U,
> },
> + .nr_extents = 1,
> },
> },
> .gid_map = {
> - .nr_extents = 1,
> {
> .extent[0] = {
> .first = 0,
> .lower_first = 0,
> .count = 4294967295U,
> },
> + .nr_extents = 1,
> },
> },
> .projid_map = {
> - .nr_extents = 1,
> {
> .extent[0] = {
> .first = 0,
> .lower_first = 0,
> .count = 4294967295U,
> },
> + .nr_extents = 1,
> },
> },
> .ns.count = REFCOUNT_INIT(3),
>
> ---
> base-commit: 698e7d1680544ef114203b0cf656faa0c1216ebc
> change-id: 20240910-work-uid_gid_map-cce46aee1b76
>
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-09-10 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 8:16 [PATCH] uidgid: make sure we fit into one cacheline Christian Brauner
2024-09-10 10:48 ` Mateusz Guzik
2024-09-10 13:00 ` Theodore Ts'o
2024-09-10 13:44 ` Mateusz Guzik
2024-09-10 13:51 ` Jeff Layton [this message]
2024-09-10 17:16 ` Matthew Wilcox
2024-09-10 18:50 ` Jeff Layton
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=80c0e982a5a55f6c0a0eeb4e717b9fc32d93de3f.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=amir73il@gmail.com \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.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