linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Christoph Hellwig <hch@lst.de>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] shared/011: run on all file system that support cgroup writeback
Date: Mon, 24 Jun 2019 11:08:39 -0400	[thread overview]
Message-ID: <20190624150839.GB6350@mit.edu> (raw)
In-Reply-To: <20190624134407.21365-1-hch@lst.de>

On Mon, Jun 24, 2019 at 03:44:07PM +0200, Christoph Hellwig wrote:
> Run the cgroup writeback test on xfs, for which I've just posted
> a patch to support cgroup writeback as well as ext2 and f2fs, which
> have supported cgroup writeback for a while now.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  tests/shared/011 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/shared/011 b/tests/shared/011
> index a0ac375d..96ce9d1c 100755
> --- a/tests/shared/011
> +++ b/tests/shared/011
> @@ -39,7 +39,7 @@ rm -f $seqres.full
>  # real QA test starts here
>  
>  # Modify as appropriate.
> -_supported_fs ext4 btrfs
> +_supported_fs ext2 ext4 f2fs btrfs xfs

Per my comments in another e-mail thread, given how many of the
primary file systems support cgroup-aware writeback, maybe we should
just remove the _supported_fs line and move this test to generic?

Whether we like it or not, there are more and more userspace tools
which assume that cgroup-aware writeback is a thing.

Alternatively, maybe we should have some standardized way so the
kernel can signal whether or not a particular mounted file system
supports cgroup-aware writeback?

						- Ted

  reply	other threads:[~2019-06-24 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24 13:44 [PATCH] shared/011: run on all file system that support cgroup writeback Christoph Hellwig
2019-06-24 15:08 ` Theodore Ts'o [this message]
2019-06-24 15:19   ` Darrick J. Wong
2019-06-26  3:17     ` Eryu Guan
2019-06-25  9:59   ` Christoph Hellwig

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=20190624150839.GB6350@mit.edu \
    --to=tytso@mit.edu \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --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).