On Tue, Aug 24, 2010 at 11:02:42AM +0800, Michael Rubin wrote: > On Mon, Aug 23, 2010 at 7:30 PM, Wu Fengguang <fengguang.wu@xxxxxxxxx> wrote: > > 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? > > Is this as an alternative to the vmstat counters or the per node > vmstat counters? > > In either case I am not sure /proc/pid will be sufficient. What if 20 > processes are created, write a lot of data, then quit? How do we know > about those events later? What about jobs that wake up, write data > then quit quickly? According to Documentation/accounting/taskstats.txt, it's possible to register a task for collecting its stat numbers when it quits. However I'm not sure if there are reliable ways to do this if tasks come and go very quickly. It may help to somehow automatically add the numbers to the parent process at process quit time. > If we are running many many tasks I would think the amount of time it > can take to cycle through all of them might mean we might not capture > all the data. Yes, 10k tasks may be too much to track. > The goal is to have a complete view of the dirtying and cleaning of > the pages over time. Using /proc/pid feels like it won't achieve that. Looks so. 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
