On Tue, Aug 24, 2010 at 01:45:41AM +0800, Michael Rubin wrote: > On Fri, Aug 20, 2010 at 5:48 PM, Wu Fengguang <fengguang.wu@xxxxxxxxx> wrote: > > I wonder if you'll still stick to the fake NUMA scenario two years > > later -- when memcg grows powerful enough. What do we do then? "Hey > > let's rip these counters, their major consumer has dumped them.." > > I think the counters will still be useful for NUMA also. Is there a > performance hit here I am missing to having the per node counters? > Just want to make sure we are only wondering about whether or not we > are polluting the interface? Also since we plan to change the name to > vmstat instead doesn't that make it more generic in the future? It's about the interface, I don't mind you adding the per-node vmstat entries which may be convenient for you and mostly harmless to others. My concern is, what do you think about the existing /proc/<pid>/io:write_bytes interface and is it good enough for your? You'll have to iterate through tasks to collect numbers for one job or for the whole system, however that should be easy and more flexible? Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
