Re: [PATCH 00/49] Automatic NUMA Balancing v10

From: Ingo Molnar
Date: Fri Dec 07 2012 - 06:01:09 EST



* Mel Gorman <mgorman@xxxxxxx> wrote:

> This is a full release of all the patches so apologies for the
> flood. [...]

I have yet to process all your mails, but assuming I address all
your review feedback and the latest unified tree in tip:master
shows no regression in your testing, would you be willing to
start using it for ongoing work?

It would make it much easier for me to pick up your
enhancements, fixes, etc.

> Changelog since V9
> o Migration scalability (mingo)

To *really* see migration scalability bottlenecks you need to
remove the migration-bandwidth throttling kludge from your tree
(or configure it up very high if you want to do it simple).

Some (certainly not all) of the performance regressions you
reported were certainly due to numa/core code hitting the
migration codepaths as aggressively as the workload demanded -
and hitting scalability bottlenecks.

The right approach is to hit scalability bottlenecks and fix
them.

Thanks,

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/