From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Jinyoung Choi <j-young.choi@samsung.com>, linux-block@vger.kernel.org
Subject: [PATCH 6/8] block: downgrade a bio_full call in bio_add_page
Date: Fri, 12 May 2023 06:38:59 -0700 [thread overview]
Message-ID: <20230512133901.1053543-7-hch@lst.de> (raw)
In-Reply-To: <20230512133901.1053543-1-hch@lst.de>
bio_add_page already checks that there is space in bi_size a little
earlier. So after we failed to add to an existing segment, just check
that there is another one available instead of duplicating the bi_size
check.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
block/bio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/bio.c b/block/bio.c
index 93e6bca3c2239f..89b1475de0c370 100644
--- a/block/bio.c
+++ b/block/bio.c
@@ -1126,7 +1126,7 @@ int bio_add_page(struct bio *bio, struct page *page,
__bio_try_merge_page(bio, page, len, offset, &same_page))
return len;
- if (bio_full(bio, len))
+ if (bio->bi_vcnt >= bio->bi_max_vecs)
return 0;
__bio_add_page(bio, page, len, offset);
return len;
--
2.39.2
next prev parent reply other threads:[~2023-05-12 13:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 13:38 rationalize the flow in bio_add_page and friends Christoph Hellwig
2023-05-12 13:38 ` [PATCH 1/8] block: tidy up the bio full checks in bio_add_hw_page Christoph Hellwig
2023-05-17 7:18 ` Jinyoung CHOI
2023-05-12 13:38 ` [PATCH 2/8] block: use SECTOR_SHIFT bio_add_hw_page Christoph Hellwig
2023-05-16 12:00 ` Johannes Thumshirn
2023-05-19 6:05 ` Jinyoung CHOI
2023-05-12 13:38 ` [PATCH 3/8] block: move the BIO_CLONED checks out of __bio_try_merge_page Christoph Hellwig
2023-05-16 12:01 ` Johannes Thumshirn
2023-05-19 6:08 ` Jinyoung CHOI
2023-05-12 13:38 ` [PATCH 4/8] block: move the bi_vcnt check " Christoph Hellwig
2023-05-16 12:04 ` Johannes Thumshirn
2023-05-19 6:13 ` Jinyoung CHOI
2023-05-12 13:38 ` [PATCH 5/8] block: move the bi_size overflow check in __bio_try_merge_page Christoph Hellwig
2023-05-16 12:08 ` Johannes Thumshirn
2023-05-19 6:14 ` Jinyoung CHOI
2023-05-12 13:38 ` Christoph Hellwig [this message]
2023-05-19 6:18 ` [PATCH 6/8] block: downgrade a bio_full call in bio_add_page Jinyoung CHOI
2023-05-12 13:39 ` [PATCH 7/8] block: move the bi_size update out of __bio_try_merge_page Christoph Hellwig
2023-05-19 6:27 ` Jinyoung CHOI
2023-05-12 13:39 ` [PATCH 8/8] block: don't pass a bio to bio_try_merge_hw_seg Christoph Hellwig
2023-05-19 6:30 ` Jinyoung CHOI
2023-05-19 2:27 ` rationalize the flow in bio_add_page and friends Jens Axboe
2023-05-20 1:49 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 16:54 rationalize the flow in bio_add_page and friends v2 Christoph Hellwig
2023-07-24 16:54 ` [PATCH 6/8] block: downgrade a bio_full call in bio_add_page Christoph Hellwig
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=20230512133901.1053543-7-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=j-young.choi@samsung.com \
--cc=linux-block@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