From: Uros Bizjak <ubizjak@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] namespace: Use atomic64_inc_return() in alloc_mnt_ns()
Date: Mon, 7 Oct 2024 17:02:30 +0200 [thread overview]
Message-ID: <CAFULd4atoeGkCTc+itU_ACBAcBxXPbPNOhockqCnd4Xsc75R9w@mail.gmail.com> (raw)
In-Reply-To: <20241007145034.GM4017910@ZenIV>
On Mon, Oct 7, 2024 at 4:50 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> On Mon, Oct 07, 2024 at 10:52:37AM +0200, Uros Bizjak wrote:
> > Use atomic64_inc_return(&ref) instead of atomic64_add_return(1, &ref)
> > to use optimized implementation and ease register pressure around
> > the primitive for targets that implement optimized variant.
> >
> > Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> > Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> > Cc: Christian Brauner <brauner@kernel.org>
> > Cc: Jan Kara <jack@suse.cz>
> > ---
> > fs/namespace.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/namespace.c b/fs/namespace.c
> > index 93c377816d75..9a3c251d033d 100644
> > --- a/fs/namespace.c
> > +++ b/fs/namespace.c
> > @@ -3901,7 +3901,7 @@ static struct mnt_namespace *alloc_mnt_ns(struct user_namespace *user_ns, bool a
> > }
> > new_ns->ns.ops = &mntns_operations;
> > if (!anon)
> > - new_ns->seq = atomic64_add_return(1, &mnt_ns_seq);
> > + new_ns->seq = atomic64_inc_return(&mnt_ns_seq);
>
> On which load do you see that path hot enough for the change to
> make any difference???
It is not performance, but code size improvement, as stated in the
commit message.
The difference on x86_32 (that implements atomic64_inc_return()) is:
eeb: b8 01 00 00 00 mov $0x1,%eax
ef0: 31 d2 xor %edx,%edx
ef2: b9 20 00 00 00 mov $0x20,%ecx
ef3: R_386_32 .data
ef7: e8 fc ff ff ff call ef8 <alloc_mnt_ns+0xd0>
ef8: R_386_PC32 atomic64_add_return_cx8
efc: 89 46 20 mov %eax,0x20(%esi)
eff: 89 56 24 mov %edx,0x24(%esi)
vs:
eeb: be 20 00 00 00 mov $0x20,%esi
eec: R_386_32 .data
ef0: e8 fc ff ff ff call ef1 <alloc_mnt_ns+0xc9>
ef1: R_386_PC32 atomic64_inc_return_cx8
ef5: 89 43 20 mov %eax,0x20(%ebx)
ef8: 89 53 24 mov %edx,0x24(%ebx)
Uros.
prev parent reply other threads:[~2024-10-07 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 8:52 [PATCH] namespace: Use atomic64_inc_return() in alloc_mnt_ns() Uros Bizjak
2024-10-07 11:39 ` Christian Brauner
2024-10-07 14:50 ` Al Viro
2024-10-07 14:56 ` Christian Brauner
2024-10-07 15:02 ` Uros Bizjak [this message]
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=CAFULd4atoeGkCTc+itU_ACBAcBxXPbPNOhockqCnd4Xsc75R9w@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).