Weird schedule delay time for cache_reap()

[Chen, Kenneth W]

I can't convince myself that the 2nd argument in schedule_delayed_work
called from cache_reap() function make any sense:


static void cache_reap(void *unused)
{ ...

        check_irq_on();
        up(&cache_chain_sem);
        drain_remote_pages();
        /* Setup the next iteration */
        schedule_delayed_work(&__get_cpu_var(reap_work), REAPTIMEOUT_CPUC + smp_processor_id());
}


Suppose one have a lucky 1024-processor big iron numa box,
cpu0 will do cache_reap every 2 sec (REAPTIMEOUT_CPUC = 2*HZ).
cpu512 will do cache_reap every 4 sec,
cpu1023 will do cache_reap every 6 sec.

Is the skew intentional on different CPU?  Why different interval for
different cpu#?

- Ken

-
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/