From: james.smart@broadcom.com (James Smart)
Subject: Booting from NVMe over Fabrics
Date: Sun, 25 Jun 2017 08:48:59 -0700 [thread overview]
Message-ID: <5d3ef427-45ec-82a1-76d4-059e651b17fd@broadcom.com> (raw)
In-Reply-To: <20170624071701.GC14580@lst.de>
On 6/24/2017 12:17 AM, Christoph Hellwig wrote:
> As long as you don't have weird hardware offloads (which seems rather
> pointless) there is nothing interesting in booting NVMe - yes you'll
> need NVMe-cli, and a working RDMA setup. But that's not any different
> than SRP or iSER, or NFS over RDMA, so we the distros should do the
> same for NVMe that they do for those technolog?es.
You seem to have left off FC. FC would like to boot FC-NVME the same as
it does FC-SCSI/FCP.
The main issue so far is user-level discovery. Swap, kdump, and ensuring
you have connectivity/can run while low-memory, are severely
taxed/at-risk by the user-level paradigms.
-- james
prev parent reply other threads:[~2017-06-25 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 13:06 Booting from NVMe over Fabrics Johannes Thumshirn
2017-06-24 7:17 ` Christoph Hellwig
2017-06-25 15:48 ` James Smart [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=5d3ef427-45ec-82a1-76d4-059e651b17fd@broadcom.com \
--to=james.smart@broadcom.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