From: dledford@redhat.com (Doug Ledford)
Subject: [PATCH 1/2] IB/mlx5: posting klm/mtt list inline in the send queue for reg_wr
Date: Thu, 19 Apr 2018 22:04:51 -0400 [thread overview]
Message-ID: <1524189891.11756.12.camel@redhat.com> (raw)
In-Reply-To: <CAL1RGDXbUXcrRyEtHWpBmWpbbCB6nuQVfWC1bi+4K_yp3pB0LQ@mail.gmail.com>
On Thu, 2018-04-19@14:11 -0700, roland wrote:
> > The fetch of the MTT/KLM list becomes the bottleneck in
> > number of IO operation could be done by NVMe over Fabrics
> > host driver on a single adapter as shown below.
> >
> > This patch is adding the support for inline registration
> > work request upon MTT/KLM list of size <=64B.
>
> It looks like this patch never made it upstream, and I don't see any
> discussion or reason why it might have been dropped.
>
> This still seems like a good idea - should we respin it against the latest tree?
If you want it included, then you'll have to respin it if for no other
reason than the fact that it isn't readily available in patchworks and
that's what we're using to track/grab patches now a days. I supposed I
could go hunting for it, but that's a good way to grab an out of date
patch and make a mistake by accident...
--
Doug Ledford <dledford at redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20180419/05204a93/attachment.sig>
next prev parent reply other threads:[~2018-04-20 2:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 16:38 [PATCH 0/2] Performance Improvents for Secured Mode NVMe over Fabrics and other RDMA ULPs idanb
2017-10-29 16:38 ` [PATCH 1/2] IB/mlx5: posting klm/mtt list inline in the send queue for reg_wr idanb
2017-10-29 17:09 ` Sagi Grimberg
2018-04-19 21:11 ` roland
2018-04-20 2:04 ` Doug Ledford [this message]
2018-04-20 19:07 ` Max Gurtovoy
2017-10-29 16:38 ` [PATCH 2/2] nvme-rdma: Add remote_invalidation module parameter idanb
2017-10-29 17:52 ` Jason Gunthorpe
2017-10-30 8:14 ` Sagi Grimberg
2017-10-30 8:38 ` idanb
2017-10-30 9:44 ` Sagi Grimberg
2017-10-30 10:31 ` idanb
2017-10-30 10:33 ` Sagi Grimberg
2017-10-30 12:35 ` idanb
2017-10-29 18:24 ` Chuck Lever
2017-10-30 18:18 ` Chuck Lever
2017-10-30 8:11 ` Sagi Grimberg
2017-10-30 8:45 ` idanb
2017-10-29 16:59 ` [PATCH 0/2] Performance Improvents for Secured Mode NVMe over Fabrics and other RDMA ULPs Sagi Grimberg
2017-10-29 17:09 ` Max Gurtovoy
2017-10-29 17:43 ` Leon Romanovsky
[not found] ` <AM0PR0502MB38906F57CD68C3707F8FE765C5580@AM0PR0502MB3890.eurprd05.prod.outlook.com>
2017-10-30 5:21 ` Leon Romanovsky
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=1524189891.11756.12.camel@redhat.com \
--to=dledford@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).