From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>, Eric Sandeen <sandeen@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-mm@kvack.org, cgroups@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] doc: cgroup: add f2fs and xfs to supported list for writeback
Date: Tue, 30 Jun 2020 08:59:34 -0500 [thread overview]
Message-ID: <59265a9d-ee0f-4432-3f86-00d076aeb8e8@sandeen.net> (raw)
In-Reply-To: <20200630054217.GA27221@infradead.org>
On 6/30/20 12:42 AM, Christoph Hellwig wrote:
> On Mon, Jun 29, 2020 at 02:08:09PM -0500, Eric Sandeen wrote:
>> 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 ...
>
> I'd rather remove the list of file systems. It has no chance of
> staying uptodate.
Is there any way for a user to know whether a filesytem does or doesn't
support it, in practice?
Thanks,
-Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-06-30 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 19:08 [f2fs-dev] [PATCH] doc: cgroup: add f2fs and xfs to supported list for writeback Eric Sandeen
2020-06-30 1:18 ` Chao Yu
2020-06-30 5:42 ` Christoph Hellwig
2020-06-30 13:59 ` Eric Sandeen [this message]
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=59265a9d-ee0f-4432-3f86-00d076aeb8e8@sandeen.net \
--to=sandeen@sandeen.net \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hch@infradead.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).