Re: [PATCH 1/4] sched: make nr_running() return 32-bit

[Thomas Gleixner]

Alexey,

On Thu, Apr 22 2021 at 23:02, Alexey Dobriyan wrote:
> Creating 2**32 tasks is impossible due to futex pid limits and wasteful
> anyway. Nobody has done it.
>

this whole pile lacks useful numbers. What's the actual benefit of that
churn?

Just with the default config for one of my reference machines:

   text		data	bss	dec	 hex	 filename
16679864	6627950	1671296	24979110 17d26a6 ../build/vmlinux-before
16679894	6627950	1671296	24979140 17d26c4 ../build/vmlinux-after
------------------------------------------------------------------------
     +30

I'm truly impressed by the massive savings of this change and I'm even
more impressed by the justification:

> Bring nr_running() into 32-bit world to save on REX prefixes.

Aside of the obvious useless churn, REX prefixes are universaly true for
all architectures, right? There is a world outside x86 ...

Thanks,

        tglx