From: Jens Axboe <axboe@fb.com>
To: Ming Lei <ming.lei@canonical.com>, <linux-kernel@vger.kernel.org>
Cc: <linux-block@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
"Mike Christie" <mchristi@redhat.com>,
Hannes Reinecke <hare@suse.com>,
Keith Busch <keith.busch@intel.com>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH] block: bio: kill BIO_MAX_SIZE
Date: Thu, 9 Jun 2016 21:35:15 -0600 [thread overview]
Message-ID: <575A3573.7010401@fb.com> (raw)
In-Reply-To: <1465529234-31195-1-git-send-email-ming.lei@canonical.com>
On 06/09/2016 09:27 PM, Ming Lei wrote:
> No one need this macro now, so remove it. Basically
> only how many bvecs in one bio matters instead
> of how many bytes in this bio.
>
> The motivation is for supporting multipage bvecs, in
> which we only know what the max count of bvecs is supported
> in the bio.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2016-06-10 3:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 3:27 [PATCH] block: bio: kill BIO_MAX_SIZE Ming Lei
2016-06-10 3:35 ` Jens Axboe [this message]
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=575A3573.7010401@fb.com \
--to=axboe@fb.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=ming.lei@canonical.com \
--cc=snitzer@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).