[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <c8271324-9132-388c-5242-d7699f011892@redhat.com>
Date: Mon, 29 Jun 2020 14:08:09 -0500
From: Eric Sandeen <sandeen@...hat.com>
To: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Jonathan Corbet <corbet@....net>
Cc: cgroups@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
linux-xfs <linux-xfs@...r.kernel.org>
Subject: [PATCH] doc: cgroup: add f2fs and xfs to supported list for writeback
f2fs and xfs have both added support for cgroup writeback:
578c647 f2fs: implement cgroup writeback support
adfb5fb xfs: implement cgroup aware writeback
so add them to the supported list in the docs.
Signed-off-by: Eric Sandeen <sandeen@...hat.com>
---
TBH I wonder about the wisdom of having this detail in
the doc, as it apparently gets missed quite often ...
diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
index ce3e05e..4f82afa 100644
--- a/Documentation/admin-guide/cgroup-v2.rst
+++ b/Documentation/admin-guide/cgroup-v2.rst
@@ -1684,9 +1684,9 @@ per-cgroup dirty memory states are examined and the more restrictive
of the two is enforced.
cgroup writeback requires explicit support from the underlying
-filesystem. Currently, cgroup writeback is implemented on ext2, ext4
-and btrfs. On other filesystems, all writeback IOs are attributed to
-the root cgroup.
+filesystem. Currently, cgroup writeback is implemented on ext2, ext4,
+btrfs, f2fs, and xfs. On other filesystems, all writeback IOs are
+attributed to the root cgroup.
There are inherent differences in memory and writeback management
which affects how cgroup ownership is tracked. Memory is tracked per
Powered by blists - more mailing lists