mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: Yury Norov <yury.norov@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Alexander Potapenko <glider@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	netdev@vger.kernel.org, linux-btrfs@vger.kernel.org,
	dm-devel@redhat.com, ntfs3@lists.linux.dev,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 04/11] linkmode: convert linkmode_{test,set,clear,mod}_bit() to macros
Date: Mon, 13 Nov 2023 20:08:40 +0100	[thread overview]
Message-ID: <33967a01-9ed0-43db-a615-907abab989b7@lunn.ch> (raw)
In-Reply-To: <20231113173717.927056-5-aleksander.lobakin@intel.com>

On Mon, Nov 13, 2023 at 06:37:10PM +0100, Alexander Lobakin wrote:
> Since commit b03fc1173c0c ("bitops: let optimize out non-atomic bitops
> on compile-time constants"), the non-atomic bitops are macros which can
> be expanded by the compilers into compile-time expressions, which will
> result in better optimized object code. Unfortunately, turned out that
> passing `volatile` to those macros discards any possibility of
> optimization, as the compilers then don't even try to look whether
> the passed bitmap is known at compilation time. In addition to that,
> the mentioned linkmode helpers are marked with `inline`, not
> `__always_inline`, meaning that it's not guaranteed some compiler won't
> uninline them for no reason, which will also effectively prevent them
> from being optimized (it's a well-known thing the compilers sometimes
> uninline `2 + 2`).
> Convert linkmode_*_bit() from inlines to macros. Their calling
> convention are 1:1 with the corresponding bitops, so that it's not even
> needed to enumerate and map the arguments, only the names. No changes in
> vmlinux' object code (compiled by LLVM for x86_64) whatsoever, but that
> doesn't necessarily means the change is meaningless.
> 
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Acked-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Alexander Lobakin <aleksander.lobakin@intel.com>

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  reply	other threads:[~2023-11-13 19:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 17:37 [PATCH v3 00/11] bitmap: prereqs for ip_tunnel flags conversion Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 01/11] bitops: add missing prototype check Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 02/11] bitops: make BYTES_TO_BITS() treewide-available Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 03/11] bitops: let the compiler optimize {__,}assign_bit() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 04/11] linkmode: convert linkmode_{test,set,clear,mod}_bit() to macros Alexander Lobakin
2023-11-13 19:08   ` Andrew Lunn [this message]
2023-11-13 17:37 ` [PATCH v3 05/11] s390/cio: rename bitmap_size() -> idset_bitmap_size() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 06/11] fs/ntfs3: add prefix to bitmap_size() and use BITS_TO_U64() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 07/11] btrfs: rename bitmap_set_bits() -> btrfs_bitmap_set_bits() Alexander Lobakin
2023-11-14  0:48   ` Anand Jain
2023-11-13 17:37 ` [PATCH v3 08/11] tools: move alignment-related macros to new <linux/align.h> Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 09/11] bitmap: introduce generic optimized bitmap_size() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 10/11] bitmap: make bitmap_{get,set}_value8() use bitmap_{read,write}() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 11/11] lib/bitmap: add compile-time test for __assign_bit() optimization Alexander Lobakin
2023-11-20 11:04 ` [PATCH v3 00/11] bitmap: prereqs for ip_tunnel flags conversion Alexander Lobakin

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=33967a01-9ed0-43db-a615-907abab989b7@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=aleksander.lobakin@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dm-devel@redhat.com \
    --cc=glider@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=netdev@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=przemyslaw.kitszel@intel.com \
    --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

all inboxes | Powered by JetHome®