From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 2/3] nvme: introduce max_segments controller attribute
Date: Tue, 22 Aug 2017 11:40:35 +0200 [thread overview]
Message-ID: <20170822094035.GA10045@lst.de> (raw)
In-Reply-To: <64ff7c30-cfb7-0e66-6882-59349faf8fc2@mellanox.com>
On Tue, Aug 22, 2017@12:36:49PM +0300, Max Gurtovoy wrote:
>> So for now to be safe it might be a good idea to always use a 4k
>> MR page size..
>>
>
> So should I send a fix only for the MR page size (4k) for now ?
> Or should we add the infrastructure for virt_boundary and max_segments per
> ctrl too ?
We'll eventually want both, but for 4.13 fixing the MR page size to
4k should be fine.
next prev parent reply other threads:[~2017-08-22 9:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 10:20 [PATCH 1/3] nvme: add virt boundary per ctrl Max Gurtovoy
2017-08-16 10:20 ` [PATCH 2/3] nvme: introduce max_segments controller attribute Max Gurtovoy
2017-08-16 13:29 ` Sagi Grimberg
2017-08-16 14:35 ` Max Gurtovoy
2017-08-16 19:04 ` Sagi Grimberg
2017-08-17 7:40 ` Christoph Hellwig
2017-08-20 6:35 ` Sagi Grimberg
2017-08-22 6:32 ` Christoph Hellwig
2017-08-22 9:36 ` Max Gurtovoy
2017-08-22 9:40 ` Christoph Hellwig [this message]
2017-08-16 10:21 ` [PATCH 3/3] nvme-rdma: fix virtual boundary calculation Max Gurtovoy
2017-08-21 22:45 ` [PATCH 1/3] nvme: add virt boundary per ctrl James Smart
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=20170822094035.GA10045@lst.de \
--to=hch@lst.de \
/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