From: Anand Jain <Anand.Jain@oracle.com>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: introduce BTRFS_IOC_GET_DEVS
Date: Mon, 27 Jan 2014 17:08:12 +0800 [thread overview]
Message-ID: <52E621FC.4010908@oracle.com> (raw)
In-Reply-To: <20140127084709.GK3314@carfax.org.uk>
On 01/27/2014 04:47 PM, Hugo Mills wrote:
> On Mon, Jan 27, 2014 at 04:52:50PM +0800, Anand Jain wrote:
>> The user land progs needs a simple way to read
>> the raw list of disks and its parameters as
>> btrfs kernel understands it. This patch will
>> introduce BTRFS_IOC_GET_DEVS which dumps
>> every thing under fs_devices.
>>
>> As of now btrfs-devlist uses this ioctl.
>>
>> In the long run this ioctl would help to optimize
>> some part of btrfs-progs, mainly the current
>> btrfs filesystem show
>
> Just thinking out loud here, really, but can we export this
> information in /sys instead, rather than adding yet more ioctls?
>
I was more inclined towards (live) memory dump. But I need to fix
btrfs-progs as well so ioctl.
next prev parent reply other threads:[~2014-01-27 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 8:52 [PATCH] dump device list as seen by the kernel Anand Jain
2014-01-27 8:52 ` [PATCH] btrfs: introduce BTRFS_IOC_GET_DEVS Anand Jain
2014-01-27 8:47 ` Hugo Mills
2014-01-27 9:08 ` Anand Jain [this message]
2014-02-06 19:49 ` David Sterba
2014-02-06 20:09 ` Goffredo Baroncelli
2014-02-06 22:05 ` David Sterba
2014-02-07 10:08 ` Anand Jain
2014-02-07 10:20 ` Hugo Mills
2014-02-12 16:01 ` David Sterba
2014-02-12 16:15 ` Hugo Mills
2014-02-25 17:45 ` David Sterba
2014-02-26 2:34 ` Anand Jain
2014-01-27 8:56 ` [PATCH] btrfs-progs: introduce btrfs-devlist Anand Jain
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=52E621FC.4010908@oracle.com \
--to=anand.jain@oracle.com \
--cc=hugo@carfax.org.uk \
--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).