From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH] nvmet: bump NVMET_NR_QUEUES to 128
Date: Thu, 14 Sep 2017 11:36:48 -0700 [thread overview]
Message-ID: <ee9de017-69e9-670e-b763-1eea73598d66@gmail.com> (raw)
In-Reply-To: <20170914170300.GA1235@infradead.org>
On 9/14/2017 10:03 AM, Christoph Hellwig wrote:
> This looks ok as a quick check, but any chance you could send
> a patch to make this configurable through configfs? Preferably
> also for the max queue size.
Yep - I'll put one together
-- james
next prev parent reply other threads:[~2017-09-14 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 23:14 [PATCH] nvmet: bump NVMET_NR_QUEUES to 128 James Smart
2017-09-12 11:59 ` Max Gurtovoy
2017-09-14 17:03 ` Christoph Hellwig
2017-09-14 18:36 ` James Smart [this message]
2017-10-05 7:52 ` Christoph Hellwig
2017-10-04 7:46 ` Christoph Hellwig
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=ee9de017-69e9-670e-b763-1eea73598d66@gmail.com \
--to=jsmart2021@gmail.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).