linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Alexander Lobakin <alobakin@pm.me>,
	Alexey Klimov <aklimov@redhat.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-mips@vger.kernel.org
Cc: Yury Norov <yury.norov@gmail.com>
Subject: [PATCH 0/2] arch: enable GENERIC_FIND_FIRST_BIT for MIPS and ARM64
Date: Thu, 25 Feb 2021 05:56:58 -0800	[thread overview]
Message-ID: <20210225135700.1381396-1-yury.norov@gmail.com> (raw)

MIPS and ARM64 don't implement find_first_{zero}_bit in arch code and
don't enable it in config. It leads to using find_next_bit() which is
less efficient:

It's beneficial to enable GENERIC_FIND_FIRST_BIT as this functionality
is not new at all and well-tested. It provides more optimized code and
saves .text memory:

Alexander Lobakin (1):
  MIPS: enable GENERIC_FIND_FIRST_BIT

Yury Norov (1):
  arm64: enable GENERIC_FIND_FIRST_BIT

 arch/arm64/Kconfig | 1 +
 arch/mips/Kconfig  | 1 +
 2 files changed, 2 insertions(+)

-- 
2.25.1


             reply	other threads:[~2021-02-25 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 13:56 Yury Norov [this message]
2021-02-25 13:56 ` [RESEND PATCH 1/2] ARM64: enable GENERIC_FIND_FIRST_BIT Yury Norov
2021-02-25 14:02   ` Will Deacon
2021-03-03 22:17     ` Yury Norov
2021-03-05 11:20       ` Catalin Marinas
2021-02-25 13:57 ` [PATCH 2/2] MIPS: " Yury Norov
2021-02-26  1:22   ` Huacai Chen
2021-02-26  4:07     ` Yury Norov
2021-03-01 14:49   ` Thomas Bogendoerfer
2021-03-15 19:14 ` (subset) [PATCH 0/2] arch: enable GENERIC_FIND_FIRST_BIT for MIPS and ARM64 Catalin Marinas

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=20210225135700.1381396-1-yury.norov@gmail.com \
    --to=yury.norov@gmail.com \
    --cc=aklimov@redhat.com \
    --cc=alobakin@pm.me \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).