From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: <linux-kernel@vger.kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH] cpumask: introduce assign_cpu() macro
Date: Mon, 27 May 2024 11:48:54 +0200 [thread overview]
Message-ID: <8a4efd9c-8416-4267-b5cf-b2aca80b03f4@intel.com> (raw)
In-Reply-To: <20240524185828.1582494-1-yury.norov@gmail.com>
From: Yury Norov <yury.norov@gmail.com>
Date: Fri, 24 May 2024 11:58:28 -0700
> Now that assign_bit() is a thin macro wrapper around set_bit() and
> clear_bit(), we can use it in cpumask API and drop duplicating
> implementations of set_cpu_xxx() helpers with no additional overhead.
>
> Bloat-o-meter reports almost 2k less of generated code for allyesconfig,
> mostly in kernel/cpu.c:
> add/remove: 2/4 grow/shrink: 3/4 up/down: 498/-2228 (-1730)
Nice save!
>
> Signed-off-by: Yury Norov <yury.norov@gmail.com>
Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>
Thanks,
Olek
prev parent reply other threads:[~2024-05-27 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 18:58 [PATCH] cpumask: introduce assign_cpu() macro Yury Norov
2024-05-27 9:48 ` Alexander Lobakin [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=8a4efd9c-8416-4267-b5cf-b2aca80b03f4@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=yury.norov@gmail.com \
/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