Re: [PATCH] mm: migrate: set demotion targets differently

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

 



On 3/29/22 04:52, Jagdish Gediya wrote:
> The current implementation to identify the demotion
> targets limits some of the opportunities to share
> the demotion targets between multiple source nodes.

This changelog is a bit unsatisfying.  It basically says: the current
code isn't working, throw some more code at the problem.

I'd love to see some more information about *why* the current code
doesn't work.  Is it purely a bug or was it mis-designed?

I actually wrote it intending for it to handle cases like you describe
while not leaving lots of nodes without demotion targets.




[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