From: Gabriel de Perthuis <g2p.code@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [survey] sysfs layout for btrfs
Date: Tue, 18 Aug 2015 08:33:20 +0000 (UTC) [thread overview]
Message-ID: <mquqkg$vh9$1@ger.gmane.org> (raw)
In-Reply-To: 55CE7C78.1020509@oracle.com
On Sat, 15 Aug 2015 07:40:40 +0800, Anand Jain wrote:
> Hello,
>
> as of now btrfs sysfs does not include the attributes for the volume
> manager part in its sysfs layout, so its being developed and there are
> two types of layout here below, so I have a quick survey to know which
> will be preferred. contenders are:
> 1. FS and VM (volume manager) attributes[1] merged sysfs layout
>
> /sys/fs/btrfs/<fsid> <-- holds FS attr, VM attr will be added here.
> /sys/fs/btrfs/<fsid>/devices/<uuid [2] > <-- btrfs_devices attr here
My vote is for the first one.
Lengthening the UI/API with /pools/ seems unnecessary, and it's
better to get attributes exposed earlier.
> 2. FS and VM attributes separated sysfs layout.
>
> /sys/fs/btrfs/<fsid> <--- as is, will continue to hold fs attributes.
> /sys/fs/btrfs/pools/<fsid>/ <-- will hold VM attributes
> /sys/fs/btrfs/pools/<fsid>/devices/<sdx> <-- btrfs_devices attr here
next prev parent reply other threads:[~2015-08-18 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 23:40 [survey] sysfs layout for btrfs Anand Jain
2015-08-18 8:33 ` Gabriel de Perthuis [this message]
2015-08-18 12:34 ` Goffredo Baroncelli
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='mquqkg$vh9$1@ger.gmane.org' \
--to=g2p.code@gmail.com \
--cc=linux-btrfs@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).