Messages in this thread | | | Date | Tue, 29 Mar 2022 07:31:12 -0700 | From | Dave Hansen <> | Subject | Re: [PATCH] mm: migrate: set demotion targets differently |
| |
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.
| |