Re: Tracking actual disk write sources instead of flush thread

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Phillip Susi <psusi@xxxxxxxxxx> writes:
>
> That seems like a severe defect.  How can such a defect be tolerated
> in this day and age?  Why does the io accounting not track how many
> pages the process dirties rather than how many it actually initiates
> the writeout for?

There is no per process dirty counter anyways.

The exiting proces write counter is legacy and generally useless.

If you want to track syscalls there are already plenty of ways
to do that per process. There's no way to track background
mmap flushes and it may be meaningless in this case anyways.


-Andi

-- 
ak@xxxxxxxxxxxxxxx -- Speaking for myself only
--
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




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux