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@xxxxxxx +49 911 74053 688 SUSE Software Solutions Germany GmbH, 90409 Nürnberg GF: F. Imendörffer, HRB 36809 (AG Nürnberg)
