[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e48ab50f-ce8a-4426-b72b-8c0f66fe80ad@huaweicloud.com>
Date: Tue, 17 Jun 2025 10:25:15 +0800
From: Zhang Yi <yi.zhang@...weicloud.com>
To: "Martin K. Petersen" <martin.petersen@...cle.com>,
Christian Brauner <brauner@...nel.org>
Cc: linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-block@...r.kernel.org, dm-devel@...ts.linux.dev,
linux-nvme@...ts.infradead.org, linux-scsi@...r.kernel.org,
linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org, hch@....de,
tytso@....edu, djwong@...nel.org, john.g.garry@...cle.com,
bmarzins@...hat.com, chaitanyak@...dia.com, shinichiro.kawasaki@....com,
yi.zhang@...wei.com, chengzhihao1@...wei.com, yukuai3@...wei.com,
yangerkun@...wei.com
Subject: Re: [PATCH 00/10] fallocate: introduce FALLOC_FL_WRITE_ZEROES flag
On 2025/6/17 0:59, Martin K. Petersen wrote:
>
> Christian,
>
>>> This looks OK to me as long as the fs folks agree on the fallocate()
>>> semantics.
>>
>> That looks overall fine. Should I queue this up in the vfs tree?
>
> We're expecting another revision addressing the queue limit sysfs
> override. Otherwise I believe it's good to go.
>
Yeah, I'm going to revise the queue limits sysfs interface as
Christoph and Darrick suggested and send out v2.
Best regards,
Yi.
Powered by blists - more mailing lists