From: Eric Sandeen <sandeen@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Jonathan Corbet <corbet@lwn.net>
Cc: cgroups@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-xfs <linux-xfs@vger.kernel.org>
Subject: [PATCH] doc: cgroup: add f2fs and xfs to supported list for writeback
Date: Mon, 29 Jun 2020 14:08:09 -0500 [thread overview]
Message-ID: <c8271324-9132-388c-5242-d7699f011892@redhat.com> (raw)
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@redhat.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
next reply other threads:[~2020-06-29 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 19:08 Eric Sandeen [this message]
2020-06-30 1:18 ` [PATCH] doc: cgroup: add f2fs and xfs to supported list for writeback Chao Yu
2020-06-30 5:42 ` Christoph Hellwig
2020-06-30 13:59 ` Eric Sandeen
2020-07-01 8:32 ` Christoph Hellwig
2020-07-01 13:25 ` Eric Sandeen
2020-07-05 20:35 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c8271324-9132-388c-5242-d7699f011892@redhat.com \
--to=sandeen@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).