On Thu, 20 Jun 2024 at 13:20, Yury Norov wrote:
>
> FORCE_NR_CPUS helped to generate a better code for me back then. I'll
> check again against the current kernel.
Of _course_ it generates better code.
But when "better code" is a source of bugs, and isn't actually useful
in general, it's not bet
On Thu, Jun 20, 2024 at 12:26:18PM -0700, Linus Torvalds wrote:
> On Thu, 20 Jun 2024 at 11:32, Yury Norov wrote:
> >
> > Is that in master already? I didn't get any email, and I can't find
> > anything related in the master branch.
>
> It's 5d272dd1b343 ("cpumask: limit FORCE_NR_CPUS to just the
On Thu, 20 Jun 2024 at 11:32, Yury Norov wrote:
>
> Is that in master already? I didn't get any email, and I can't find
> anything related in the master branch.
It's 5d272dd1b343 ("cpumask: limit FORCE_NR_CPUS to just the UP case").
> > New rule: before you send some optimization, you need to ha
On Thu, Jun 20, 2024 at 11:00:38AM -0700, Linus Torvalds wrote:
> On Thu, 20 Jun 2024 at 10:57, Yury Norov wrote:
> >
> >
> > The typical lock-protected bit allocation may look like this:
>
> If it looks like this, then nobody cares. Clearly the user in question
> never actually cared about perfo
On Thu, 20 Jun 2024 at 10:57, Yury Norov wrote:
>
>
> The typical lock-protected bit allocation may look like this:
If it looks like this, then nobody cares. Clearly the user in question
never actually cared about performance, and you SHOULD NOT then say
"let's optimize this that nobody cares abo
---
This v4 moves new API to separate headers, as adding stuff to find.h
concerns people, particularly Linus. It also adds few more conversions
alongside other cosmetic changes. See full changelog below.
---
Add helpers around test_and_{set,clear}_bit() to allow searching for
clear or set bits
