From: Keith Busch <kbusch@kernel.org>
To: Jaehoon Shim <jmattshim@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-nvme@lists.infradead.org
Subject: Re: [LSF/MM/BPF TOPIC] Adding NVMeVirt to Kernel mainline
Date: Thu, 22 Feb 2024 08:56:33 -0700 [thread overview]
Message-ID: <ZddusYydcaBkY24T@kbusch-mbp> (raw)
In-Reply-To: <CABj8AyhLjBkQUhp4CFY+xV4_GwDAyzU251St+BMoYUKCjj7M9Q@mail.gmail.com>
On Thu, Feb 22, 2024 at 10:38:03AM +0900, Jaehoon Shim wrote:
> Hi all,
>
> My research group has recently introduced NVMeVirt, a software-defined
> virtual NVMe device implemented as a Linux kernel module. Upon
> loading, NVMeVirt emulates an NVMe device that is recognized by the
> host as a native PCIe device.
> - https://github.com/snu-csl/nvmevirt
> - https://www.usenix.org/system/files/fast23-kim.pdf
>
> Advantages of NVMeVirt are:
> - Deployable in real environments (not virtual)
> - PCI peer-to-peer DMA support
It looks like your module creates a single nvme device. How are you
testing P2P with just one device?
next prev parent reply other threads:[~2024-02-22 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 1:38 [LSF/MM/BPF TOPIC] Adding NVMeVirt to Kernel mainline Jaehoon Shim
2024-02-22 7:10 ` Damien Le Moal
2024-02-23 5:38 ` Jaehoon Shim
2024-02-22 15:56 ` Keith Busch [this message]
2024-02-23 5:45 ` Jaehoon Shim
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=ZddusYydcaBkY24T@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=jmattshim@gmail.com \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).