All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Guoqing Jiang <guoqing.jiang@linux.dev>,
	song@kernel.org, linux-raid@vger.kernel.org,
	jens@chianterastutte.eu, linux-block@vger.kernel.org
Subject: Re: [PATCH] raid1: ensure bio doesn't have more than BIO_MAX_VECS sectors
Date: Mon, 16 Aug 2021 19:40:48 +0800	[thread overview]
Message-ID: <YRpOwFewTw4imskn@T590> (raw)
In-Reply-To: <YRox8gMjl/Y5Yt/k@infradead.org>

On Mon, Aug 16, 2021 at 10:37:54AM +0100, Christoph Hellwig wrote:
> On Sat, Aug 14, 2021 at 04:57:06PM +0800, Ming Lei wrote:
> > > +	if (bitmap)
> > > +		max_sectors = min_t(int, max_sectors, BIO_MAX_VECS * PAGE_SIZE);
> > 
> > s/PAGE_SIZE/PAGE_SECTORS
> 
> Yeah, max_sectors is in size units, I messed that up.
> 
> > 
> > > +
> > >  	if (max_sectors < bio_sectors(bio)) {
> > >  		struct bio *split = bio_split(bio, max_sectors,
> > >  					      GFP_NOIO, &conf->bio_split);
> > > 
> > 
> > Here the limit is max single-page vectors, and the above way may not work,
> > such as:
> > 
> > 0 ~ 254: each bvec's length is 512
> > 255: bvec's length is 8192
> > 
> > the total length is just 512*255 + 8192 = 138752 bytes = 271 sectors, but it
> > still may need 257 bvecs, which can't be allocated via bio_alloc_bioset().
> 
> Yes, we still need the rounding magic that alloc_behind_master_bio uses
> here.

But it is wrong to use max sectors to limit number of bvecs(segments), isn't it?


Thanks,
Ming


  reply	other threads:[~2021-08-16 11:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13  6:05 [PATCH] raid1: ensure bio doesn't have more than BIO_MAX_VECS sectors Guoqing Jiang
2021-08-13  7:49 ` Christoph Hellwig
2021-08-13  8:38   ` Guoqing Jiang
2021-08-14  7:55     ` Christoph Hellwig
2021-08-14  8:57       ` Ming Lei
2021-08-16  6:27         ` Guoqing Jiang
2021-08-16  7:13           ` Ming Lei
2021-08-16  9:37         ` Christoph Hellwig
2021-08-16 11:40           ` Ming Lei [this message]
2021-08-17  5:06             ` Christoph Hellwig
2021-08-17 12:32               ` Ming Lei
2021-09-24 15:34                 ` Jens Stutte (Archiv)
2021-09-25 23:02                   ` Guoqing Jiang
2021-08-13  9:27 ` kernel test robot
2021-08-13  9:27   ` kernel test robot
2021-08-13 10:12 ` kernel test robot
2021-08-13 10:12   ` kernel test robot

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=YRpOwFewTw4imskn@T590 \
    --to=ming.lei@redhat.com \
    --cc=guoqing.jiang@linux.dev \
    --cc=hch@infradead.org \
    --cc=jens@chianterastutte.eu \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.