Re: [PATCH 3/3] writeback: tracking subsystems causing writeback

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

 



Michael Rubin <mrubin@xxxxxxxxxx> writes:
>
>     # cat /sys/block/sda/bdi/writeback_stats
>     balance dirty pages                       0
>     balance dirty pages waiting               0
>     periodic writeback                    92024
>     periodic writeback exited                 0
>     laptop periodic                           0
>     laptop or bg threshold                    0
>     free more memory                          0
>     try to free pages                       271
>     syc_sync                                  6
>     sync filesystem                           0

That exports a lot of kernel internals in /sys, presumably read by some
applications. What happens with the applications if the kernel internals
ever change?  Will the application break?

It would be bad to not be able to change the kernel because of
such an interface.

-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