From: Dave Chinner <david@fromorbit.com>
To: Sarthak Kukreti <sarthakkukreti@chromium.org>
Cc: dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>, Mike Snitzer <snitzer@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@lst.de>, Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH v9 0/3] [PATCH v9 0/3] Introduce provisioning primitives
Date: Sat, 11 Nov 2023 11:56:52 +1100 [thread overview]
Message-ID: <ZU7RVKJIzm8ExGGH@dread.disaster.area> (raw)
In-Reply-To: <20231110010139.3901150-1-sarthakkukreti@chromium.org>
On Thu, Nov 09, 2023 at 05:01:35PM -0800, Sarthak Kukreti wrote:
> Hi,
>
> This patch series is version 9 of the patch series to introduce
> block-level provisioning mechanism (original [1]), which is useful for
> provisioning space across thinly provisioned storage architectures (loop
> devices backed by sparse files, dm-thin devices, virtio-blk). This
> series has minimal changes over v8[2], with a couple of patches dropped
> (suggested by Dave).
>
> This patch series is rebased from the linux-dm/dm-6.5-provision-support
> [3] on to (a12deb44f973 Merge tag 'input-for-v6.7-rc0' ...). The final
> patch in the series is a blktest (suggested by Dave in 4) which was used
> to test out the provisioning flow for loop devices on sparse files on an
> ext4 filesystem.
What happened to the XFS patch I sent to support provisioning for
fallocate() operations through XFS?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2023-11-11 0:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 1:01 [PATCH v9 0/3] [PATCH v9 0/3] Introduce provisioning primitives Sarthak Kukreti
2023-11-10 1:01 ` [PATCH v9 1/3] block: " Sarthak Kukreti
2023-11-10 1:01 ` [PATCH v9 2/3] dm: Add block provisioning support Sarthak Kukreti
2023-11-10 1:01 ` [PATCH v9 3/3] loop: Add support for provision requests Sarthak Kukreti
2023-11-10 1:01 ` [PATCH] loop/010: Add test for mode 0 fallocate() on loop devices Sarthak Kukreti
2023-11-10 1:27 ` Yi Zhang
2023-11-10 6:25 ` Sarthak Kukreti
2023-11-11 0:56 ` Dave Chinner [this message]
2023-11-13 21:26 ` [PATCH v9 0/3] [PATCH v9 0/3] Introduce provisioning primitives Sarthak Kukreti
2023-11-20 20:33 ` Dave Chinner
2023-11-20 23:59 ` Sarthak Kukreti
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=ZU7RVKJIzm8ExGGH@dread.disaster.area \
--to=david@fromorbit.com \
--cc=axboe@kernel.dk \
--cc=bfoster@redhat.com \
--cc=djwong@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sarthakkukreti@chromium.org \
--cc=snitzer@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