From: swise@opengridcomputing.com (Steve Wise)
Subject: [PATCH v4 0/3] NVMF/RDMA 16K Inline Support
Date: Tue, 19 Jun 2018 11:02:48 -0500 [thread overview]
Message-ID: <68434eaa-ab12-35a2-2625-55978b9a7cf8@opengridcomputing.com> (raw)
In-Reply-To: <20180619054056.GB23184@lst.de>
On 6/19/2018 12:40 AM, Christoph Hellwig wrote:
> On Mon, Jun 18, 2018@10:18:18AM -0500, Steve Wise wrote:
>>
>> On 6/18/2018 9:49 AM, Steve Wise wrote:
>>> Hey Christoph,? will you merge patches 2 and 3 for -next?? I think
>>> they're ready.?? I also have a nvmetcli patch I can send out for using
>>> param_inline_data_size.
>>>
>>>
>> Or I can rebase on 4.18-rc1 and resend...
> Yes, please do. I'd also like to see at least an ACK from one or our
> RDMA low level experts.
>
Sure.
+doug and jason.
There is one merge issue: This series will require the max_send/recv_sge
commit, which is merged in rdma-next [1] just recently.? Perhaps you can
pull that from the linux-rdma repo if and when these 2 nvme patches are
pulled into your repo?? I think that will allow easy merging when the
block and rdma repos get merged into Linus' repo.
Steve.
[1] https://www.spinics.net/lists/linux-rdma/msg66118.html
next prev parent reply other threads:[~2018-06-19 16:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 17:22 [PATCH v4 0/3] NVMF/RDMA 16K Inline Support Steve Wise
2018-06-05 17:16 ` [PATCH v4 1/3] nvme-rdma: correctly check for target keyed sgl support Steve Wise
2018-06-06 12:31 ` Christoph Hellwig
2018-06-05 17:16 ` [PATCH v4 2/3] nvme-rdma: support up to 4 segments of inline data Steve Wise
2018-06-05 17:16 ` [PATCH v4 3/3] nvmet-rdma: support max(16KB, PAGE_SIZE) " Steve Wise
2018-06-06 9:24 ` Sagi Grimberg
2018-06-07 19:53 ` Steve Wise
2018-06-19 11:59 ` Sagi Grimberg
2018-06-19 14:35 ` Steve Wise
2018-06-19 19:29 ` Steve Wise
2018-06-18 14:49 ` [PATCH v4 0/3] NVMF/RDMA 16K Inline Support Steve Wise
2018-06-18 15:18 ` Steve Wise
2018-06-19 5:40 ` Christoph Hellwig
2018-06-19 9:21 ` Max Gurtovoy
2018-06-19 14:41 ` Steve Wise
2018-06-19 16:02 ` Steve Wise [this message]
2018-06-19 17:43 ` Jason Gunthorpe
2018-06-20 8:24 ` Christoph Hellwig
2018-06-20 14:02 ` Steve Wise
2018-06-20 18:03 ` Jason Gunthorpe
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=68434eaa-ab12-35a2-2625-55978b9a7cf8@opengridcomputing.com \
--to=swise@opengridcomputing.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