public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: yanzheng@21cn.com
Cc: linux-btrfs@vger.kernel.org, chris.mason@oracle.com
Subject: Re: [PATCH] Snapshot/subvolume listing feature
Date: Mon, 16 Nov 2009 17:58:29 +0900	[thread overview]
Message-ID: <4B011435.2080005@jp.fujitsu.com> (raw)
In-Reply-To: <3d0408630911160015t79044d72u3489a42d57c6f844@mail.gmail.com>

Thank you for your advice.

I'm aware of redundant search, but I didn't think of
getdents like interface.

I'll remake it without redundant search.

Regards,
taruisi

Yan, Zheng wrote:
> 2009/11/16 TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>:
>> I made Snapshot/subvolume listing feature.
>>
>> This feature consists of two patches, for kernel(ioctl),
>> and for progs(btrfsctl). I send these two patches as response
>> of this mail soon.
>>
>> New option '-l' is introduced to btrfsctl for listing.
>>
>> If this option is specified, btrfsctl call new ioctl. New ioctl
>> searches root tree and enumerates subtrees. For each subtrees,
>> ioctl searches directory path to tree root, and enumerates
>> more descendant until no more subtree is found.
>>
>> MANPAGE-like option description and examples are as follows.
>>
>>  OPTIONS
>>        -l _file_
>>                List all snapshot/subvolume directories under a tree
>>                which _file_ belongs to.
>>
>>  EXAMPLES
>>        # btrfsctl -l /work/btrfs
>>    Base path = /work/btrfs/
>>    No.    Tree ID      Subvolume Relative Path
>>     1         256      ss1/
>>     2         257      ss2/
>>     3         258      svs1/ss1/
>>     4         259      svs1/ss2/
>>     5         260      svs2/ss1/
>>     6         261      svs2/ss2/
>>     7         262      ss3/
>>     8         263      ss4/
>>     9         264      sv_pool/
>>    10         265      sv_pool/ss01/
>>    11         266      sv_pool/ss02/
>>    12         267      sv_pool/ss03/
>>    13         268      sv_pool/ss04/
>>    14         269      sv_pool/ss05/
>>    15         270      sv_pool/ss06/
>>    16         271      sv_pool/ss07/
>>    17         272      sv_pool/ss08/
>>    18         273      sv_pool/ss09/
>>    19         274      sv_pool/ss10/
>>  operation complete
>>  Btrfs v0.19-9-gd67dad2
>>
> 
> Thank you for doing this.
> 
> I have a quick look at the patches. It seems the ioctl returns full path
> to each subvolume and uses sequence ID to indicate the progress
> of listing. Every time the ioctl is called, it tries building full list of
> subvolume, then skip entries that already returned.  I think the API is
> suboptimal, a getdents like API is better. (The ioctl only lists subvolumes
> within a given subvolume, the user program call the ioctl recursively
> to list all subvolumes.)
> 
> Yan, Zheng
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2009-11-16  8:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16  1:42 [PATCH] Snapshot/subvolume listing feature TARUISI Hiroaki
2009-11-16  1:44 ` [PATCH] Subvolume Listing feature for ioctl TARUISI Hiroaki
2009-11-16  1:45 ` [PATCH] Subvolume Listing feature for btrfsctl TARUISI Hiroaki
2009-11-16  3:06 ` [PATCH] Snapshot/subvolume listing feature TARUISI Hiroaki
2009-11-16  8:15 ` Yan, Zheng 
2009-11-16  8:58   ` TARUISI Hiroaki [this message]
2009-11-16 13:00     ` Andrey Kuzmin
2009-11-18  5:39     ` TARUISI Hiroaki
2009-11-18  5:42       ` [PATCH] Subvolume listing feature for ioctl TARUISI Hiroaki
2009-12-11 20:57         ` Josef Bacik
2009-12-12  0:31           ` TARUISI Hiroaki
2009-11-18  5:43       ` [PATCH] Subvolume listing feature for btrfsctl TARUISI Hiroaki

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=4B011435.2080005@jp.fujitsu.com \
    --to=taruishi.hiroak@jp.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=yanzheng@21cn.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