Re: [PATCH] selftests/seccomp: Pin benchmark to single CPU

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Feb 06, 2024 at 01:56:47AM -0800, Kees Cook wrote:

> +	/* Set from highest CPU down. */
> +	for (cpu = ncores - 1; cpu >= 0; cpu--) {
> +		CPU_ZERO_S(setsz, setp);
> +		CPU_SET_S(cpu, setsz, setp);

Is there some particular reason to go from the highest CPU number down?
Not that it super matters but the default would be to iterate from 0 and
there's a comment but it just says the what not the why.

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux