linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Yi <yi.zhang@huaweicloud.com>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	hch@lst.de, tytso@mit.edu, djwong@kernel.org,
	john.g.garry@oracle.com, bmarzins@redhat.com,
	chaitanyak@nvidia.com, shinichiro.kawasaki@wdc.com,
	martin.petersen@oracle.com, yi.zhang@huawei.com,
	chengzhihao1@huawei.com, yukuai3@huawei.com,
	yangerkun@huawei.com, linux-fsdevel@vger.kernel.org,
	linux-ext4@vger.kernel.org, linux-block@vger.kernel.org,
	dm-devel@lists.linux.dev, linux-nvme@lists.infradead.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2 0/9] fallocate: introduce FALLOC_FL_WRITE_ZEROES flag
Date: Thu, 3 Jul 2025 11:35:41 +0800	[thread overview]
Message-ID: <99010bfd-c968-49c7-b62b-c72b38722c1b@huaweicloud.com> (raw)
In-Reply-To: <20250623-woanders-allabendlich-f87ae2d9c704@brauner>

On 2025/6/23 18:46, Christian Brauner wrote:
> On Thu, 19 Jun 2025 19:17:57 +0800, Zhang Yi wrote:
>> From: Zhang Yi <yi.zhang@huawei.com>
>>
>> Changes since v1:
>>  - Rebase codes on 6.16-rc2.
>>  - Use max_{hw|user}_wzeroes_unmap_sectors queue limits instead of
>>    BLK_FEAT_WRITE_ZEROES_UNMAP feature to represent the status of the
>>    unmap write zeroes operation as Christoph and Darrick suggested. This
>>    redoes the first 5 patches, so remove all the reviewed-by tags,
>>    please review them again.
>>  - Simplify the description of FALLOC_FL_WRITE_ZEROES in patch 06 as
>>    Darrick suggested.
>>  - Revise the check order of FALLOC_FL_WRITE_ZEROES in patch 08 as
>>    Christoph suggested.
>> Changes since RFC v4:
>>  - Rebase codes on 6.16-rc1.
>>  - Add a new queue_limit flag, and change the write_zeroes_unmap sysfs
>>    interface to RW mode. User can disable the unmap write zeroes
>>    operation by writing '0' to it when the operation is slow.
>>  - Modify the documentation of write_zeroes_unmap sysfs interface as
>>    Martin suggested.
>>  - Remove the statx interface.
>>  - Make the bdev and ext4 don't allow to submit FALLOC_FL_WRITE_ZEROES
>>    if the block device does not enable the unmap write zeroes operation,
>>    it should return -EOPNOTSUPP.
>> Changes sicne RFC v3:
>>  - Rebase codes on 6.15-rc2.
>>  - Add a note in patch 1 to indicate that the unmap write zeros command
>>    is not always guaranteed as Christoph suggested.
>>  - Rename bdev_unmap_write_zeroes() helper and move it to patch 1 as
>>    Christoph suggested.
>>  - Introduce a new statx attribute flag STATX_ATTR_WRITE_ZEROES_UNMAP as
>>    Christoph and Christian suggested.
>>  - Exchange the order of the two patches that modified
>>    blkdev_fallocate() as Christoph suggested.
>> Changes since RFC v2:
>>  - Rebase codes on next-20250314.
>>  - Add support for nvme multipath.
>>  - Add support for NVMeT with block device backing.
>>  - Clear FALLOC_FL_WRITE_ZEROES if dm clear
>>    limits->max_write_zeroes_sectors.
>>  - Complement the counterpart userspace tools(util-linux and xfs_io)
>>    and tests(blktests and xfstests), please see below for details.
>> Changes since RFC v1:
>>  - Switch to add a new write zeroes operation, FALLOC_FL_WRITE_ZEROES,
>>    in fallocate, instead of just adding a supported flag to
>>    FALLOC_FL_ZERO_RANGE.
>>  - Introduce a new flag BLK_FEAT_WRITE_ZEROES_UNMAP to the block
>>    device's queue limit features, and implement it on SCSI sd driver,
>>    NVMe SSD driver and dm driver.
>>  - Implement FALLOC_FL_WRITE_ZEROES on both the ext4 filesystem and
>>    block device (bdev).
>>
>> [...]
> 
> If needed, the branch can be declared stable and thus be used as base
> for other work.
> 
> ---
> 
> Applied to the vfs-6.17.fallocate branch of the vfs/vfs.git tree.
> Patches in the vfs-6.17.fallocate branch should appear in linux-next soon.
> 
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
> 
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
> 
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs-6.17.fallocate

Hi Christian,

I noticed that this patch series doesn't appear to be merged into this
branch. Just wondering if it might have been missed?

Best regards,
Yi.

> 
> [1/9] block: introduce max_{hw|user}_wzeroes_unmap_sectors to queue limits
>       https://git.kernel.org/vfs/vfs/c/2695a9b086fd
> [2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit
>       https://git.kernel.org/vfs/vfs/c/bf07c1180194
> [3/9] nvmet: set WZDS and DRB if device enables unmap write zeroes operation
>       https://git.kernel.org/vfs/vfs/c/a6c7ab5adcba
> [4/9] scsi: sd: set max_hw_wzeroes_unmap_sectors if device supports SD_ZERO_*_UNMAP
>       https://git.kernel.org/vfs/vfs/c/92372ed1cc88
> [5/9] dm: clear unmap write zeroes limits when disabling write zeroes
>       https://git.kernel.org/vfs/vfs/c/e383d550e716
> [6/9] fs: introduce FALLOC_FL_WRITE_ZEROES to fallocate
>       https://git.kernel.org/vfs/vfs/c/1ed1b5df86ec
> [7/9] block: factor out common part in blkdev_fallocate()
>       https://git.kernel.org/vfs/vfs/c/96433508c8c0
> [8/9] block: add FALLOC_FL_WRITE_ZEROES support
>       https://git.kernel.org/vfs/vfs/c/2b4e5f9b3eb9
> [9/9] ext4: add FALLOC_FL_WRITE_ZEROES support
>       https://git.kernel.org/vfs/vfs/c/51954e469396



  reply	other threads:[~2025-07-03  3:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 11:17 [PATCH v2 0/9] fallocate: introduce FALLOC_FL_WRITE_ZEROES flag Zhang Yi
2025-06-19 11:17 ` [PATCH v2 1/9] block: introduce max_{hw|user}_wzeroes_unmap_sectors to queue limits Zhang Yi
2025-06-23  5:39   ` Christoph Hellwig
2025-08-21 12:55   ` John Garry
2025-08-23  4:37     ` Zhang Yi
2025-06-19 11:17 ` [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit Zhang Yi
2025-06-23  5:40   ` Christoph Hellwig
2025-06-19 11:18 ` [PATCH v2 3/9] nvmet: set WZDS and DRB if device enables unmap write zeroes operation Zhang Yi
2025-06-23  5:40   ` Christoph Hellwig
2025-06-19 11:18 ` [PATCH v2 4/9] scsi: sd: set max_hw_wzeroes_unmap_sectors if device supports SD_ZERO_*_UNMAP Zhang Yi
2025-06-19 11:18 ` [PATCH v2 5/9] dm: clear unmap write zeroes limits when disabling write zeroes Zhang Yi
2025-06-19 11:18 ` [PATCH v2 6/9] fs: introduce FALLOC_FL_WRITE_ZEROES to fallocate Zhang Yi
2025-06-19 11:18 ` [PATCH v2 7/9] block: factor out common part in blkdev_fallocate() Zhang Yi
2025-06-19 11:18 ` [PATCH v2 8/9] block: add FALLOC_FL_WRITE_ZEROES support Zhang Yi
2025-06-19 11:18 ` [PATCH v2 9/9] ext4: " Zhang Yi
2025-06-23 10:46 ` [PATCH v2 0/9] fallocate: introduce FALLOC_FL_WRITE_ZEROES flag Christian Brauner
2025-07-03  3:35   ` Zhang Yi [this message]
2025-07-04  8:39     ` Christian Brauner
2025-06-23 15:08 ` Martin K. Petersen
2025-06-26 13:57   ` Zhang Yi

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=99010bfd-c968-49c7-b62b-c72b38722c1b@huaweicloud.com \
    --to=yi.zhang@huaweicloud.com \
    --cc=bmarzins@redhat.com \
    --cc=brauner@kernel.org \
    --cc=chaitanyak@nvidia.com \
    --cc=chengzhihao1@huawei.com \
    --cc=djwong@kernel.org \
    --cc=dm-devel@lists.linux.dev \
    --cc=hch@lst.de \
    --cc=john.g.garry@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=tytso@mit.edu \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).