From: hch@lst.de (Christoph Hellwig)
Subject: [PATCHv1] nvmet-rdma: Support 16K worth of inline data for write commands
Date: Wed, 8 Feb 2017 09:31:10 +0100 [thread overview]
Message-ID: <20170208083110.GC7629@lst.de> (raw)
In-Reply-To: <1486507882-23688-1-git-send-email-parav@mellanox.com>
Hi Parav,
I like this in principle, but I'm really worried about the resource
consumption of just enabling this by default. I think we need
a tunable in configfs for the max inline data, and for the queue
depth at least, and maybe reduce the queue depth a bit by default
to compensate for the much higher per-queue memory usage.
next prev parent reply other threads:[~2017-02-08 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 22:51 [PATCHv1] nvmet-rdma: Support 16K worth of inline data for write commands Parav Pandit
2017-02-08 8:31 ` Christoph Hellwig [this message]
2017-02-08 15:19 ` Parav Pandit
2017-02-08 9:58 ` Sagi Grimberg
2017-02-08 16:03 ` Parav Pandit
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=20170208083110.GC7629@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