public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Cc: Conrad Meyer <[email protected]>,
	[email protected], [email protected],
	Christoph Hellwig <[email protected]>
Subject: Re: [PATCH v3 7/8] block: add nowait flag for __blkdev_issue_zero_pages
Date: Fri, 6 Sep 2024 14:46:18 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 9/6/24 14:41, Jens Axboe wrote:
> On 9/4/24 8:18 AM, Pavel Begunkov wrote:
>> diff --git a/block/blk-lib.c b/block/blk-lib.c
>> index c94c67a75f7e..a16b7c7965e8 100644
>> --- a/block/blk-lib.c
>> +++ b/block/blk-lib.c
>> @@ -193,20 +193,32 @@ static unsigned int __blkdev_sectors_to_bio_pages(sector_t nr_sects)
>>   	return min(pages, (sector_t)BIO_MAX_VECS);
>>   }
>>   
>> -static void __blkdev_issue_zero_pages(struct block_device *bdev,
>> +int blkdev_issue_zero_pages_bio(struct block_device *bdev,
>>   		sector_t sector, sector_t nr_sects, gfp_t gfp_mask,
>>   		struct bio **biop, unsigned int flags)
>>   {
>> +	blk_opf_t opf = REQ_OP_WRITE;
>> +
>> +	if (flags & BLKDEV_ZERO_PAGES_NOWAIT) {
>> +		sector_t max_bio_sectors = BIO_MAX_VECS << PAGE_SECTORS_SHIFT;
>> +
>> +		if (nr_sects > max_bio_sectors)
>> +			return -EAGAIN;
>> +		opf |= REQ_NOWAIT;
>> +	}
>> +
>>   	while (nr_sects) {
>>   		unsigned int nr_vecs = __blkdev_sectors_to_bio_pages(nr_sects);
>>   		struct bio *bio;
>>   
>>   		bio = bio_alloc(bdev, nr_vecs, REQ_OP_WRITE, gfp_mask);
> 
> as per the kernel test bot, I guess this one should be using opf rather
> than REQ_OP_WRITE.

Right, I overlooked it. I'm going to resend the series later today.

-- 
Pavel Begunkov

  reply	other threads:[~2024-09-06 13:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 14:17 [PATCH v3 0/8] implement async block discards and other ops via io_uring Pavel Begunkov
2024-09-04 14:18 ` [PATCH v3 1/8] io_uring/cmd: expose iowq to cmds Pavel Begunkov
2024-09-04 14:18 ` [PATCH v3 2/8] io_uring/cmd: give inline space in request " Pavel Begunkov
2024-09-04 14:18 ` [PATCH v3 3/8] filemap: introduce filemap_invalidate_pages Pavel Begunkov
2024-09-04 14:18 ` [PATCH v3 4/8] block: introduce blk_validate_byte_range() Pavel Begunkov
2024-09-04 14:18 ` [PATCH v3 5/8] block: implement async discard as io_uring cmd Pavel Begunkov
2024-09-04 14:18 ` [PATCH v3 6/8] block: implement async write zeroes command Pavel Begunkov
2024-09-04 14:18 ` [PATCH v3 7/8] block: add nowait flag for __blkdev_issue_zero_pages Pavel Begunkov
2024-09-06  3:23   ` kernel test robot
2024-09-06 13:41   ` Jens Axboe
2024-09-06 13:46     ` Pavel Begunkov [this message]
2024-09-04 14:18 ` [PATCH v3 8/8] block: implement async write zero pages command Pavel Begunkov

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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