From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: hch <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>, Jens Axboe <axboe@kernel.dk>,
"bhelgaas@google.com" <bhelgaas@google.com>,
Jason Gunthorpe <jgg@nvidia.com>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"yi.l.liu@intel.com" <yi.l.liu@intel.com>,
"alex@awilliam.me" <alex@awilliam.me>
Subject: Announcement: NVMe Live Migration Software Working Group
Date: Tue, 19 May 2026 23:56:39 +0000 [thread overview]
Message-ID: <3e566eb1-db29-4eef-b88d-a7978a1d1a4f@nvidia.com> (raw)
Hi,
I’m pleased to announce that the NVMe Board of Directors has approved
the formation of the NVMe Live Migration Software Working Group
(NVMe LM SW WG), see [1].
What?
The NVMe LM SW WG will focus on building an end-to-end Linux kernel
solution that follows the NVMe-approved specification and helps ensure
the implementation is aligned with the specification before it is
proposed upstream.
Why?
NVMe Live Migration is one of the more complex features we have
developed over the last four years. The NVMe Board has recognized the
need for a centralized effort around this work. Please bring any related
questions, use cases, or implementation topics to the NVMe LM SW WG.
How?
I am one of the co-chairs of the NVMe LM SW WG and will be coordinating
this effort within the TWG and with the upstream Linux kernel community.
Please reach out to me if your organization is interested in participating.
The prerequisites are that your organization must be a member of the
NVMe TWG and must sign an agreement to participate in the
NVMe LM SW WG. Linux Foundation membership is not required to
participate in this working group.
I look forward to working with you.
_This email is approved by the NVMe Board._
Best regards,
Chaitanya Kulkarni
Co-Chair, NVMe Live Migration Software Working Group
[1] Background
We started this work in August 2022, and it has evolved significantly
over time — from the original SDC 2022 research paper (thanks to
Dr. Stephen Bates) to the NVMe-approved specification.
I've also posted two RFCs to keep the ongoing development aligned with the
kernel community and received valuable feedback from kernel patch
reviews. Thanks to Christoph, Jason, Alex, and others; their input has
helped shape the technical specification.
reply other threads:[~2026-05-19 23:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3e566eb1-db29-4eef-b88d-a7978a1d1a4f@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=alex@awilliam.me \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=kbusch@kernel.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=yi.l.liu@intel.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