From: Jens Axboe <axboe@fb.com>
To: Josef Bacik <josef@toxicpanda.com>, <axboe@kernel.dk>,
<nbd-general@lists.sourceforge.net>,
<linux-block@vger.kernel.org>, <kernel-team@fb.com>
Subject: Re: [PATCH] nbd: set the max segment size to UINT_MAX
Date: Wed, 19 Apr 2017 08:16:22 -0600 [thread overview]
Message-ID: <e6c114e2-aa3f-829a-fb40-dd901d77d406@fb.com> (raw)
In-Reply-To: <1492546971-2682-1-git-send-email-jbacik@fb.com>
On 04/18/2017 02:22 PM, Josef Bacik wrote:
> NBD doesn't care about limiting the segment size, let the user push the
> largest bio's they want. This allows us to control the request size
> solely through max_sectors_kb.
Thanks Josef, applied for 4.12.
--
Jens Axboe
next prev parent reply other threads:[~2017-04-19 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 20:22 [PATCH] nbd: set the max segment size to UINT_MAX Josef Bacik
2017-04-19 0:54 ` Ming Lei
2017-04-19 14:16 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-17 13:44 Josef Bacik
2017-04-17 15:55 ` Jens Axboe
2017-04-17 15:57 ` Jens Axboe
2017-04-17 15:59 ` Jens Axboe
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=e6c114e2-aa3f-829a-fb40-dd901d77d406@fb.com \
--to=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=nbd-general@lists.sourceforge.net \
/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