On 2020-11-10 09:36, Greg Kroah-Hartman wrote:
[...]
While punting the logic out to userspace is simple for the kernel, and
of course my first option, I think this isn't going to work in the
long-run and the kernel will have to "know" what type of process it is
scheduling in order to correctly deal with this nightmare as userspace
can't do that well, if at all.
For that to happen, we must first decide which part of the userspace
ABI we are prepared to compromise on. The most obvious one would be to
allow overriding the affinity on exec, but I'm pretty sure it has bad
interactions with cgroups, on top of violating the existing ABI which
mandates that the affinity is inherited across exec.
There may be other options (always make at least one 32bit-capable CPU
part of the process affinity?), but they all imply some form of
userspace
visible regressions.
Pick your poison... :-/
M.
--
Jazz is not dead. It just smells funny...
