From: Anand Jain <anand.jain@oracle.com>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/6] btrfs-progs: add support for LOGICAL_INO_V2 features in logical-resolve
Date: Mon, 2 Dec 2019 19:02:26 +0800 [thread overview]
Message-ID: <3d8298c5-bab4-67f5-2bf7-8156865d949f@oracle.com> (raw)
In-Reply-To: <20191127035509.15011-1-ce3g8jdj@umail.furryterror.org>
On 27/11/19 11:55 AM, Zygo Blaxell wrote:
> This patch set adds support for LOGICAL_INO_V2 features:
>
> - bigger buffer size (16M instead of 64K, default also increased to 64K)
>
> - IGNORE_OFFSETS flag to look up references by extent instead of block
>
> If the V2 options are used, it calls the V2 ioctl; otherwise, it calls
> the V1 ioctl for old kernel compatibility.
>
>
For the whole series.
Reviewed-by: Anand Jain <anand.jain@oracle.com>
(Nit: This should be v4 as this patch was submitted before:
https://lore.kernel.org/linux-btrfs/20170922175847.6071-1-ce3g8jdj@umail.furryterror.org/T/#t
)
next prev parent reply other threads:[~2019-12-02 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 3:55 [PATCH 0/6] btrfs-progs: add support for LOGICAL_INO_V2 features in logical-resolve Zygo Blaxell
2019-11-27 3:55 ` [PATCH 1/6] btrfs-progs: ioctl-test: add LOGICAL_INO_V2 Zygo Blaxell
2019-11-27 3:55 ` [PATCH 2/6] btrfs-progs: libbtrfsutil: " Zygo Blaxell
2019-11-27 3:55 ` [PATCH 3/6] btrfs-progs: add LOGICAL_INO_V2 to ioctl.h Zygo Blaxell
2019-11-27 3:55 ` [PATCH 4/6] btrfs-progs: inspect: add support for LOGICAL_INO_V2 ioctl Zygo Blaxell
2019-11-27 3:55 ` [PATCH 5/6] btrfs-progs: inspect: increase logical-resolve default buffer size to 64K Zygo Blaxell
2019-11-27 3:55 ` [PATCH 6/6] btrfs-progs: inspect-internal: document new logical-resolve options and kernel requirements Zygo Blaxell
2019-12-02 11:02 ` Anand Jain [this message]
2019-12-02 18:42 ` [PATCH 0/6] btrfs-progs: add support for LOGICAL_INO_V2 features in logical-resolve Zygo Blaxell
2019-12-03 1:08 ` Anand Jain
2020-01-02 19:00 ` David Sterba
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=3d8298c5-bab4-67f5-2bf7-8156865d949f@oracle.com \
--to=anand.jain@oracle.com \
--cc=ce3g8jdj@umail.furryterror.org \
--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).