Hi Ben,

Bumping this thread since I've been having some new thoughts on the issue now that we are starting integration with newer spdk versions.

Unfortunately the merge isn't as smooth as I'd like it to be since the bdev module is pretty tightly integrated into spdk, perhaps we made some false assumptions writing the module, but it seems some of the newer spdk features are complicating the integration.

My question is, if this passthrough module is useful, wouldn't it be better to maintain it as part of spdk so that we can catch issues as soon as they show up?

We would be happy to help with maintaining this module, the module with is currently part of our CI with our "frozen" spdk version, but once integrated into the newer version we choose, I'll add it to the CI our CI as well.


From: SPDK <spdk-bounces@lists.01.org> on behalf of Walker, Benjamin <benjamin.walker@intel.com>
Sent: Friday, February 2, 2018 11:43:58 PM
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK + user space appliance
On Thu, 2018-02-01 at 08:29 +0000, Shahar Salzman wrote:
> Hi Ben,
> Would you also like to take a look at the bdev_user module?
> It still needs some patching (as some of the stuff is still hard coded), but I
> think we can get most of it cleaned up in a couple of days.
> In any case, is it the intention that the user write his own bdev module, or
> would this user appliance glue be a useful generic module?

For existing storage stacks that serve block I/O, like the internals of a SAN,
the idea is that you write your own bdev module to forward I/O coming out of the
SPDK bdev layer. Then you can use the SPDK iSCSI/NVMe-oF/vhost targets mostly

In some cases, the actual iSCSI/NVMe-oF/vhost target applications won't
integrate nicely directly into an existing storage application because they
spawn their own threads and allocate their own memory. To support that, the
libraries may be consumed directly instead of the applications (lib/iscsi,
lib/scsi, lib/nvmf, etc.). The libraries don't spawn any of their own threads,
but instead rely on SPDK's abstractions in include/spdk/io_channel.h. See


We don't currently have a way to write a custom bdev module that resides outside
of the SPDK source tree, but it's very possible to add support for that. But
beyond that inconvenience (just drop your module in lib/bdev for now), writing a
bdev module is the recommended way of interacting with the bottom end of the
SPDK bdev layer. I think that's what you really want to be doing in your code,
from what I can tell.

I hope that helps!
SPDK mailing list