Re: [LSF/MM/BPF TOPIC] block drivers in user space

From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagi@grimberg.me>,
	Gabriel Krisman Bertazi <krisman@collabora.com>,
	lsf-pc@lists.linux-foundation.org,
	Mike Christie <michael.christie@oracle.com>
Cc: linux-block@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] block drivers in user space
Date: Tue, 22 Feb 2022 18:46:07 +0100	[thread overview]
Message-ID: <c67683ac-b13a-23b6-3e50-e07ee2b88606@suse.de> (raw)
In-Reply-To: <b6bb4435-d83c-b129-c761-00a74e7e0739@grimberg.me>

On 2/22/22 15:46, Sagi Grimberg wrote:
> 
>> Actually, I'd rather have something like an 'inverse io_uring', where
>> an application creates a memory region separated into several 'ring'
>> for submission and completion.
>> Then the kernel could write/map the incoming data onto the rings, and
>> application can read from there.
>> Maybe it'll be worthwhile to look at virtio here.
> 
> There is lio loopback backed by tcmu... I'm assuming that nvmet can
> hook into the same/similar interface. nvmet is pretty lean, and we
> can probably help tcmu/equivalent scale better if that is a concern...

Yeah; maybe. I've had a look at tcmu, but it would need to be updated to
handle multiple rings.
Mike? What'd you say?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		        Kernel Storage Architect
hare@suse.de			               +49 911 74053 688
SUSE Software Solutions Germany GmbH, 90409 Nürnberg
GF: F. Imendörffer, HRB 36809 (AG Nürnberg)