From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH RFC 0/2] 8K Inline Support
Date: Fri, 11 May 2018 08:19:47 +0200 [thread overview]
Message-ID: <20180511061947.GB7962@lst.de> (raw)
In-Reply-To: <cover.1525880285.git.swise@opengridcomputing.com>
On Wed, May 09, 2018@08:38:05AM -0700, Steve Wise wrote:
> For small nvmf write IO over the rdma transport, it is advantagous to
> make use of inline mode to avoid the latency of the target issuing an
> rdma read to fetch the data. Currently inline is used for <= 4K writes.
> 8K, though, requires the rdma read. For iWARP transports additional
> latency is incurred because the target mr of the read must be registered
> with remote write access. By allowing 2 pages worth of inline payload,
> I see a reduction in 8K nvmf write latency of anywhere from 2-7 usecs
> depending on the RDMA transport..
>
> Is this a worthwhile change? I think it is. Please comment!
I think this came up before. I'm fine with supporting larger sizes,
but I really want the size configurable. We can argue about the
default separately.
prev parent reply other threads:[~2018-05-11 6:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:38 [PATCH RFC 0/2] 8K Inline Support Steve Wise
2018-05-09 14:31 ` [PATCH RFC 1/2] nvme-rdma: Support 8K inline Steve Wise
2018-05-09 16:55 ` Parav Pandit
2018-05-09 19:28 ` Steve Wise
2018-05-11 6:48 ` Christoph Hellwig
2018-05-14 18:33 ` Steve Wise
2018-05-09 14:34 ` [PATCH RFC 2/2] nvmet-rdma: " Steve Wise
2018-05-14 10:16 ` Max Gurtovoy
2018-05-14 14:58 ` Steve Wise
2018-05-09 18:46 ` [PATCH RFC 0/2] 8K Inline Support Steve Wise
2018-05-11 6:19 ` Christoph Hellwig [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=20180511061947.GB7962@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;
as well as URLs for NNTP newsgroup(s).