linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: btrfs: Add new 'limit' test group for btrfs
Date: Tue, 2 Jan 2018 17:24:00 +0100	[thread overview]
Message-ID: <20180102162400.GV3553@twin.jikos.cz> (raw)
In-Reply-To: <20171226055744.27697-1-wqu@suse.com>

On Tue, Dec 26, 2017 at 01:57:44PM +0800, Qu Wenruo wrote:
> Btrfs qgroup also supports to limit the usage of specified qgroups.
> 
> It's possible to enable qgroup but doesn't enable limit.
> (Most user won't use qgroup limit for various problems)
> 
> So add a new test group 'limit' for btrfs, as a subset of existing
> 'qgroup' group.

The term 'limit' is IMHO too generic, qglimit or qg_limit would be more
descriptive.

      reply	other threads:[~2018-01-02 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-26  5:57 [PATCH] fstests: btrfs: Add new 'limit' test group for btrfs Qu Wenruo
2018-01-02 16:24 ` David Sterba [this message]

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=20180102162400.GV3553@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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).