All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@canonical.com>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: Jens Axboe <axboe@fb.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-block@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Eric Wheeler <bcache@lists.ewheeler.net>,
	Sebastian Roesner <sroesner-kernelorg@roesner-online.de>,
	"4.2+" <stable@vger.kernel.org>, Shaohua Li <shli@fb.com>
Subject: Re: [PATCH] block: make sure big bio is splitted into at most 256 bvecs
Date: Wed, 6 Apr 2016 10:37:05 +0800	[thread overview]
Message-ID: <CACVXFVPD=fb3iFwY9xO7s_daZ-gePiXKQs7XEO48vCGx+WSOzg@mail.gmail.com> (raw)
In-Reply-To: <20160406023411.GA7793@kmo-pixel>

On Wed, Apr 6, 2016 at 10:34 AM, Kent Overstreet
<kent.overstreet@gmail.com> wrote:
> On Wed, Apr 06, 2016 at 10:30:22AM +0800, Ming Lei wrote:
>> Now limit.max_segments is for limiting segments from hw view, one this
>> segment may include lots of pages/bvecs.
>>
>> The current bio_clone() issue is that we can't clone from one bio which
>> includes more than 256 bvecs, maybe all these 256 bvecs belong to
>> one same hw segment.
>
> So the distinction is purely a post multipage bvec thing?

Even after multipage bvec is applied, the limit for max bvecs is still needed
for some cases like bio bounce, in which bio_clone() need to
clone single page bvec.

Thanks,


> --
> To unsubscribe from this list: send the line "unsubscribe linux-block" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-04-06  2:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 17:44 [PATCH] block: make sure big bio is splitted into at most 256 bvecs Ming Lei
2016-04-05 18:27 ` Shaohua Li
2016-04-06  0:27   ` Kent Overstreet
2016-04-06  0:30     ` Shaohua Li
2016-04-06  0:36       ` Kent Overstreet
2016-04-06  0:41         ` Shaohua Li
2016-04-06  0:45           ` Kent Overstreet
2016-04-06  0:59             ` Shaohua Li
2016-04-06  1:05               ` Ming Lei
2016-04-06  0:47   ` Ming Lei
2016-04-06  1:04     ` Shaohua Li
2016-04-06  1:11       ` Ming Lei
2016-04-06  0:30 ` Kent Overstreet
2016-04-06  0:59   ` Ming Lei
2016-04-06  1:10     ` Kent Overstreet
2016-04-06  1:20       ` Ming Lei
2016-04-06  1:28         ` Kent Overstreet
2016-04-06  1:51           ` Ming Lei
2016-04-06  2:22             ` Kent Overstreet
2016-04-06  2:30               ` Ming Lei
2016-04-06  2:34                 ` Kent Overstreet
2016-04-06  2:37                   ` Ming Lei [this message]
2016-04-06  2:40                     ` Kent Overstreet
2016-04-06  2:51                       ` Ming Lei
2016-04-06  2:58                         ` Kent Overstreet
2016-04-06  1:02 ` Ming Lei
2016-04-07  1:48   ` Eric Wheeler
2016-04-07  1:36 ` Eric Wheeler
2016-04-07  1:49   ` Ming Lei
2016-04-07  1:56     ` Eric Wheeler
2016-04-07  2:16       ` Ming Lei
2016-04-07 23:29         ` Eric Wheeler
2016-04-08  0:21           ` Ming Lei

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='CACVXFVPD=fb3iFwY9xO7s_daZ-gePiXKQs7XEO48vCGx+WSOzg@mail.gmail.com' \
    --to=ming.lei@canonical.com \
    --cc=axboe@fb.com \
    --cc=bcache@lists.ewheeler.net \
    --cc=hch@infradead.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shli@fb.com \
    --cc=sroesner-kernelorg@roesner-online.de \
    --cc=stable@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 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.