Re: [RFC PATCH] mm/mempolicy: add MPOL_PREFERRED_STRICT memory policy

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

 



On Wed 13-10-21 18:53:55, Aneesh Kumar K.V wrote:
> On 10/13/21 18:46, Andi Kleen wrote:
> > 
> > > The difference with MPOL_BIND is the ability to specify a preferred node
> > > which is the first node in the nodemask argument passed.
> > 
> > That's always the one with the lowest number. Isn't that quite limiting
> > in practice?
> > 
> > It seems if you really want to do that you would need another argument.
> > 
> Yes. But that would make it a new syscall. Should we do that?

Yes, I do not see any reasonable to cram this into the existing syscall.
I am not yet sure what the syscall should look like though. I can see
two usecases, one of the is a very specific node allocation fallback
order requirement and another one is preferrence for a cpu less node
over other nodes. Both are slightly different.
-- 
Michal Hocko
SUSE Labs




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux