From: Kent Overstreet <kent.overstreet@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Wheeler <bcache@lists.ewheeler.net>,
Ming Lei <ming.lei@canonical.com>, Jens Axboe <axboe@fb.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-bcache@vger.kernel.org, linux-raid@vger.kernel.org,
Sebastian Roesner <sroesner-kernelorg@roesner-online.de>,
"4.3+" <stable@vger.kernel.org>, Shaohua Li <shli@fb.com>
Subject: Re: [PATCH v2] block: make sure big bio is splitted into at most 256 bvecs
Date: Fri, 12 Aug 2016 08:36:56 -0800 [thread overview]
Message-ID: <20160812163656.GA13370@kmo-pixel> (raw)
In-Reply-To: <20160811140253.GA2867@infradead.org>
On Thu, Aug 11, 2016 at 07:02:53AM -0700, Christoph Hellwig wrote:
> Please just fix bcache to not submit bios larger than BIO_MAX_PAGES for
> now, until we can support such callers in general and enable common
> used code to do so.
Christoph, what's wrong with Ming's patch? Leaving bcache aside, just
considering the block layer, do you think that patch is the wrong approach?
next prev parent reply other threads:[~2016-08-12 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 3:43 [PATCH v1] block: make sure big bio is splitted into at most 256 bvecs Ming Lei
2016-04-06 3:46 ` Kent Overstreet
2016-08-11 6:33 ` [PATCH v2] " Eric Wheeler
2016-08-11 14:02 ` Christoph Hellwig
2016-08-12 11:12 ` Ming Lei
2016-08-12 11:12 ` Ming Lei
2016-08-12 16:36 ` Kent Overstreet [this message]
2016-06-10 11:07 Ming Lei
2016-06-10 11:37 ` Hannes Reinecke
2016-06-10 11:37 ` Hannes Reinecke
2016-06-10 14:16 ` Ming Lei
2016-06-10 14:16 ` Ming Lei
2016-06-13 15:46 ` 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=20160812163656.GA13370@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=axboe@fb.com \
--cc=bcache@lists.ewheeler.net \
--cc=hch@infradead.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=ming.lei@canonical.com \
--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.