linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang Shilong <wangshilong1991@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: sensille@gmx.net, list.btrfs@jan-o-sch.net, wangsl.fnst@cn.fujitsu.com
Subject: [RFC PATCH 0/2] remove exclusive size from btrfs qgroup
Date: Sat,  2 Nov 2013 23:14:31 +0800	[thread overview]
Message-ID: <1383405273-27304-1-git-send-email-wangshilong1991@gmail.com> (raw)

From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>

Btrfs qgroup gives us an important feature to know a subvolume's
sole size, however, it brings some problems.

Especially, we can not make qgroup's exclusive size correct when
deleting subvolumes(we haven't found an effective way at least).

Another big problem, some users complain with qgroup enabled, system
memory cost become high.

So i am always thinking that why not implemnt it in a more simple and
direct way, we just keep qgroup's rferenced size, this will make life
simple and easy.

This is only a RFC patch, we need more discussion, and patch itself
need more testing and cleanup work.

Any comments are welcome!

Wang Shilong (2):
  Btrfs: disable qgroup's exclusive size tracking
  Btrfs: remove subvolume qgroup automatically with qgroup enabled

 fs/btrfs/ctree.h  |   2 +
 fs/btrfs/ioctl.c  |   5 +-
 fs/btrfs/qgroup.c | 330 ++++++++++++++++--------------------------------------
 3 files changed, 101 insertions(+), 236 deletions(-)

-- 
1.7.11.7


             reply	other threads:[~2013-11-02 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 15:14 Wang Shilong [this message]
2013-11-02 15:14 ` [RFC PATCH 1/2] Btrfs: disable qgroup's exclusive size tracking Wang Shilong
2013-11-02 15:14 ` [RFC PATCH 2/2] Btrfs: remove subvolume qgroup automatically with qgroup enabled Wang Shilong

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=1383405273-27304-1-git-send-email-wangshilong1991@gmail.com \
    --to=wangshilong1991@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list.btrfs@jan-o-sch.net \
    --cc=sensille@gmx.net \
    --cc=wangsl.fnst@cn.fujitsu.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).