Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Tzu-Ching Yang <shingekinocore@gmail.com>
To: Yury Norov <ynorov@nvidia.com>
Cc: Yury Norov <yury.norov@gmail.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bitops: Share the generic ffs()/fls() binary search via UNROLL()
Date: Sat, 17 Oct 2026 00:35:49 +0800	[thread overview]
Message-ID: <20261016163549.636471-1-shingekinocore@gmail.com> (raw)
In-Reply-To: <atJN_MOFxvqOM9h2@yury>

On Fri, Oct 16, 2026 at 12:17:00PM -0400, Yury Norov wrote:
> Alright, so the basic idea is to hide the exact implementation behind
> the macro magic. This is highly unfavorable unless it brings substantial
> improvement i.e. in code generation. In kernel we're drifting toward the
> exactly opposite direction: getting rid of those macro tricks folded one
> into another in favor of the plain human-readable code.

Thanks for having a look and for the pointers, understood, and sorry
about the length of the description. I'm dropping this one and will
follow Arnd's suggestion instead, replacing custom arch helpers with
the builtins where that simplifies the code.

Thanks,
Tzu-Ching

      reply	other threads:[~2026-10-16 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  2:56 [PATCH] bitops: Share the generic ffs()/fls() binary search via UNROLL() Tzu-Ching Yang
2026-10-16  5:54 ` Arnd Bergmann
2026-10-16  7:16   ` Arnd Bergmann
2026-10-16 13:53     ` Tzu-Ching Yang
2026-10-16 14:49       ` Arnd Bergmann
2026-10-16 16:17 ` Yury Norov
2026-10-16 16:35   ` Tzu-Ching Yang [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=20261016163549.636471-1-shingekinocore@gmail.com \
    --to=shingekinocore@gmail.com \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=ynorov@nvidia.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