Tracking actual disk write sources instead of flush thread

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

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

A lot of disk writes, especially when they are small individual files
being written by several different processes, are hidden behind the
flush thread.  Is there no way to properly track the process actually
responsible for the IO, even when it is the flush thread that
initiates the writeout?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTTeRzAAoJEI5FoCIzSKrw9WUH/jTozXvpeN7A0uN8KeafAhdk
agVupehoAYUDzDdYP3+JDkCmp5vgymzZydFasrPyLHmVqGsnojr/s/r6BowiQT73
Nks90Po+5wsburECDiuRz91POBbE5PTu0laK0fJWpTqeX+gZUlZBuNQlz8B2s2dr
wwtnN7tSVPc+H7TVrJz5CI/zW+rVjADXuA5GEshXg3/jfh9UnA/W5kKEVSbBvo7t
SwLH0jQ173qbTjWMu4DQIo4mAJ+JC0fYpxnmsIDZlIdNQ3JvbnwG03eyKJiDTRE1
hWklKcxSvv6MDBWcb0fhbIcLhfnQGGFq16szkQO1KmBg1/MDe7HSEncc+MooQOc=
=3C3I
-----END PGP SIGNATURE-----
--
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