From: hch@infradead.org (Christoph Hellwig)
Subject: NVMe and SR-IOV, how to use together?
Date: Mon, 18 Sep 2017 09:11:48 -0700 [thread overview]
Message-ID: <20170918161148.GA310@infradead.org> (raw)
In-Reply-To: <CAO+XWgk1o26gj5n-3vszuoQqXzaLjKdevU133X3206FMzxO6rQ@mail.gmail.com>
SR-IOV itself only allows you to create new virtual functions,
you can look at any number of Linux howtos on creating them using
the sysfs interface.
As far as NVMe is concerned there are multiple levels of interaction
that could be possible, all optional.
First NVMe since version 1.1 supports subsystems with multiple
controlles, and you can use namespace management (if support by the
device) to assign namespaces to one or more controllers. On Linux
you can use the nvme-cli tool for that.
Since NVMe 1.3 there are virtualization extensions that also allow to
assign resources like queue pairs to specific VMs. There is no support
in Linux or nvme-cli for that at the moment.
next prev parent reply other threads:[~2017-09-18 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 16:38 NVMe and SR-IOV, how to use together? Bogdan Rudas
2017-09-18 16:11 ` Christoph Hellwig [this message]
2017-09-18 18:20 ` Bogdan Rudas
2017-09-18 18:41 ` Keith Busch
2017-09-19 11:30 ` Bogdan Rudas
2017-09-19 12:49 ` Gruher, Joseph R
2017-09-19 13:59 ` Bogdan Rudas
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=20170918161148.GA310@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox