Prev: [tip:x86/urgent] x86, apic: Map the local apic when parsing the MP table.
Next: first round of SCSI updates for the 2.6.36 merge window
From: Andrew Morton on 5 Aug 2010 20:30
On Fri, 6 Aug 2010 09:18:59 +0900 (JST)
KOSAKI Motohiro <kosaki.motohiro(a)jp.fujitsu.com> wrote:

> > On Thu, Aug 5, 2010 at 4:56 PM, KOSAKI Motohiro
> > <kosaki.motohiro(a)jp.fujitsu.com> wrote:
> > > /proc/vmstat already have both.
> > >
> > > cat /proc/vmstat |grep nr_dirty
> > > cat /proc/vmstat |grep nr_writeback
> > >
> > > Also, /sys/devices/system/node/node0/meminfo show per-node stat.
> > >
> > > Perhaps, I'm missing your point.
> >
> > These only show the number of dirty pages present in the system at the
> > point they are queried.
> > The counter I am trying to add are increasing over time. They allow
> > developers to see rates of pages being dirtied and entering writeback.
> > Which is very helpful.
>
> Usually administrators get the data two times and subtract them. Isn't it sufficient?
>

Nope. The existing nr_dirty is "number of pages dirtied since boot"
minus "number of pages cleaned since boot". If you do the
wait-one-second-then-subtract thing on nr_dirty, the result is
dirtying-bandwidth minus cleaning-bandwidth, and can't be used to
determine dirtying-bandwidth.

I can see that a graph of dirtying events versus time could be an
interesting thing. I don't see how it could be obtained using the
existing instrumentation. tracepoints, probably..

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [tip:x86/urgent] x86, apic: Map the local apic when parsing the MP table.
Next: first round of SCSI updates for the 2.6.36 merge window