From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH/RFC] NVMe: add support for doing offline/online of attached namespaces
Date: Fri, 23 Jan 2015 09:44:57 -0800 [thread overview]
Message-ID: <20150123174457.GA12539@infradead.org> (raw)
In-Reply-To: <54C2875A.3040502@fb.com>
On Fri, Jan 23, 2015@10:39:38AM -0700, Jens Axboe wrote:
> For the per dev host/sdev busy counters, those could be further improved if
> they turn out to be a problem. I've got various "things" here that'll do
> 1-2M IOPS per dev, so some test/profiling would not be a problem to do.
We've tested up to 3M IOPS and it wasn't an issue, but none of these
systems had more than two sockets.
> First issue is support for > 1 hw queue in SCSI, though.
We've added > 1 queue support for virtio-scsi and srp, but most HBAs lack
the hardware support for it.
next prev parent reply other threads:[~2015-01-23 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 15:24 [PATCH/RFC] NVMe: add support for doing offline/online of attached namespaces Jens Axboe
2015-01-23 17:11 ` Christoph Hellwig
2015-01-23 17:24 ` Jens Axboe
2015-01-23 17:31 ` Christoph Hellwig
2015-01-23 17:39 ` Jens Axboe
2015-01-23 17:44 ` Christoph Hellwig [this message]
2015-01-23 17:46 ` Jens Axboe
2015-01-23 17:51 ` Christoph Hellwig
2015-01-23 17:52 ` Jens Axboe
2015-01-27 20:59 ` Keith Busch
2015-01-28 16:13 ` Jens Axboe
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=20150123174457.GA12539@infradead.org \
--to=hch@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.