--- GiGiorgoseKeramidaskekeramidaeceidpupatrasr wrote:
On 2005-03-24 19:53, Jonathan Stewart [EMAIL PROTECTED] wrote:
--- Dan Nelson dndnelsonlallantgroupom wrote:
In the last episode (Mar 24), Jonathan Stewart said:
In that case how would I track how much information a process has
actually
--- Giorgos Keramidas [EMAIL PROTECTED] wrote:
On 2005-03-25 10:08, Jonathan Stewart [EMAIL PROTECTED] wrote:
--- Giorgos Keramidas keramida at ceid dot upatras dot gr wrote:
So, what you are looking for is a single byte count that
increases
sequentially for all read() and write
When I run the command ps -u -o inblock on a process reading a
262144000 byte file the highest block count I see is ~2010 but my
filesystem block size is 16384 and 262144000/16384 is 16000 so it seems
to be off by about a factor of 8. I even tried looking through the
source code for the ps command
--- Dan Nelson [EMAIL PROTECTED] wrote:
In the last episode (Mar 24), Jonathan Stewart said:
When I run the command ps -u -o inblock on a process reading a
262144000 byte file the highest block count I see is ~2010 but my
filesystem block size is 16384 and 262144000/16384 is 16000 so
--- Dan Nelson [EMAIL PROTECTED] wrote:
In the last episode (Mar 24), Jonathan Stewart said:
In that case how would I track how much information a process has
actually read from a drive? I occasionally run processes that will
read as much as 40+ gig in a single run which takes quite
