On 10/23/2011 11:56 AM, Gilad Ben-Yossef wrote:
Use a cpumask to track CPUs with per-cpu pages in any zone and only send an IPI requesting CPUs to drain these pages to the buddy allocator if they actually have pages.
+/* Which CPUs have per cpu pages */ +cpumask_var_t cpus_with_pcp; +static DEFINE_PER_CPU(unsigned long, total_cpu_pcp_count);
Does the flushing happen so frequently that it is worth keeping this state on a per-cpu basis, or would it be better to check each CPU's pcp info and assemble a cpumask at flush time like done in patch 5? -- All rights reversed -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>