On Thu, Aug 29, 2013 at 11:36:10AM -0700, Dave Hansen wrote:
> The new shrinker infrastructure in mmotm looks like it will make this
> problem worse.
>
> old code:
> shrink_slab()
> for_each_shrinker {
> do_shrinker_shrink(); // one per batch
> prune_super()
> grab_super_passive()
> }
> }
I think you've simplified it down too far. The current code does:
for_each_shrinker {
max_pass = do_shrinker_shrink(0);
// ^^ does grab_super_passive()
while(total_scan >= batch_size) {
do_shrinker_shrink(0)
// ^^ does grab_super_passive()
do_shrinker_shrink(batch_size)
// ^^ does grab_super_passive()
}
}
> Which means we've got at _most_ one grab_super_passive() per batch.
No, there's two. one count, one scan per batch.
> The new code is something like this:
>
> shrink_slab()
> {
> list_for_each_entry(shrinker, &shrinker_list, list) {
> for_each_node_mask(... shrinkctl->nodes_to_scan) {
> shrink_slab_node()
> }
> }
> }
Right, but what you are missing here is that the nodemask passed in
to shrink_slab() only has a single node bit set during reclaim -
the bit that matches the zone being reclaimed from.
drop_slab(), OTOH, does:
nodes_setall(shrink.nodes_to_scan);
before calling shrink_slab in a loopi because it's trying to free
*everything*, and that's why the shrink_slab() code handles that
case.
> shrink_slab_node()
> {
> max_pass = shrinker->count_objects(shrinker, shrinkctl);
> // ^^ does grab_super_passive()
> ...
> while (total_scan >= batch_size) {
> ret = shrinker->scan_objects(shrinker, shrinkctl);
> // ^^ does grab_super_passive()
> }
> }
>
> We've got an extra grab_super_passive()s in the case where we are
> actually doing a scan, plus we've got the extra for_each_node_mask()
> loop. That means even more lock acquisitions in the multi-node NUMA
> case, which is exactly where we want to get rid of global lock acquisitions.
I disagree. With direct memory reclaim, we have an identical number
of calls to shrink_slab() occurring, and each target a single node.
hence there is typically a 1:1 call ratio for
shrink_slab:shrink_slab_node. An because shrink_slab_node() has one
less callout per batch iteration, there is an overall reduction in
the number of grab_super_passive calls from the shrinker. Worst case
is no change, best case is a 50% reduction in the number of calls.
Cheers,
Dave.
--
Dave Chinner
da...@fromorbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
