On Mon, Jan 16, 2023 at 02:35:41PM -0600, Eric Blake wrote:
> On Wed, Jan 04, 2023 at 10:51:50PM +, Richard W.M. Jones wrote:
> > Here's an updated version which supports read, write, flush,
> > write-zeroes, discard and FUA:
> >
> > https://gitlab.com/rwmjones/nbdkit/-/commits/2023-libblkio/
On Wed, Jan 04, 2023 at 10:51:50PM +, Richard W.M. Jones wrote:
> Here's an updated version which supports read, write, flush,
> write-zeroes, discard and FUA:
>
> https://gitlab.com/rwmjones/nbdkit/-/commits/2023-libblkio/
...
> PS: Eric: One thing we lack in the NBD space is a standards
>
On Mon, Jan 16, 2023 at 04:45:28PM +0100, Stefano Garzarella wrote:
> On Mon, Jan 16, 2023 at 3:46 PM Stefano Garzarella
> wrote:
> > On Mon, Jan 16, 2023 at 03:39:29PM +0100, Stefano Garzarella wrote:
> > >On Wed, Jan 11, 2023 at 04:49:14PM +, Richard W.M. Jones wrote:
> > >>On Wed, Jan 11,
On Mon, Jan 16, 2023 at 3:46 PM Stefano Garzarella wrote:
> On Mon, Jan 16, 2023 at 03:39:29PM +0100, Stefano Garzarella wrote:
> >On Wed, Jan 11, 2023 at 04:49:14PM +, Richard W.M. Jones wrote:
> >>On Wed, Jan 11, 2023 at 11:34:50AM -0500, Stefan Hajnoczi wrote:
> >>>On Sat, Jan 07, 2023 at
On Mon, Jan 16, 2023 at 03:39:29PM +0100, Stefano Garzarella wrote:
On Wed, Jan 11, 2023 at 04:49:14PM +, Richard W.M. Jones wrote:
On Wed, Jan 11, 2023 at 11:34:50AM -0500, Stefan Hajnoczi wrote:
On Sat, Jan 07, 2023 at 07:44:37PM +, Richard W.M. Jones wrote:
This is upstream in
On Wed, Jan 11, 2023 at 04:49:14PM +, Richard W.M. Jones wrote:
On Wed, Jan 11, 2023 at 11:34:50AM -0500, Stefan Hajnoczi wrote:
On Sat, Jan 07, 2023 at 07:44:37PM +, Richard W.M. Jones wrote:
>
> This is upstream in nbdkit now:
>
On Wed, Jan 11, 2023 at 10:52:01AM -0500, Stefan Hajnoczi wrote:
> On Wed, Jan 04, 2023 at 06:14:34PM +, Richard W.M. Jones wrote:
> > (1) There is no way to know which properties are readable, writable,
> > and those which need to be set before or after blkio_connect (see
> >
On Wed, Jan 11, 2023 at 11:34:50AM -0500, Stefan Hajnoczi wrote:
> On Sat, Jan 07, 2023 at 07:44:37PM +, Richard W.M. Jones wrote:
> >
> > This is upstream in nbdkit now:
> > https://gitlab.com/nbdkit/nbdkit/-/tree/master/plugins/blkio
> >
> > Another question:
> >
> > (6) vhost-user +
On Sat, Jan 07, 2023 at 07:44:37PM +, Richard W.M. Jones wrote:
>
> This is upstream in nbdkit now:
> https://gitlab.com/nbdkit/nbdkit/-/tree/master/plugins/blkio
>
> Another question:
>
> (6) vhost-user + "read-only" property acts a bit strangely. After
> opening virtio-blk-vhost-user it
On Wed, Jan 04, 2023 at 09:43:57PM +, Richard W.M. Jones wrote:
> On Wed, Jan 04, 2023 at 06:14:34PM +, Richard W.M. Jones wrote:
> > (3) It seems like some drivers require pre-allocated memory regions,
> > and since some do that means we might as well implement this. It
> > also seems
On Wed, Jan 04, 2023 at 07:01:24PM +, Richard W.M. Jones wrote:
> (5) "The application is responsible for thread-safety. No thread
> synchronization is necessary when a queue is only used from a single
> thread. Proper synchronization is required when sharing a queue
> between multiple
On Wed, Jan 04, 2023 at 06:14:34PM +, Richard W.M. Jones wrote:
> This is an incomplete outline implementation for a libblkio plugin for
> nbdkit. At the moment it only supports reading the same ("capacity")
> of the device, and not even reading or writing. I have some questions
> about the
On Sun, Jan 08, 2023 at 08:35:35PM +, Alberto Faria wrote:
> With qemu-storage-daemon, you must set writable=on on the
> vhost-user-blk export for the device to be writable.
Ah, this was the thing I was missing, thanks.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
> On Wed, Jan 04, 2023 at 06:14:34PM +, Richard W.M. Jones wrote:
> > (3) It seems like some drivers require pre-allocated memory regions,
> > and since some do that means we might as well implement this. It
> > also seems like some drivers require file-backed pre-allocated
> > memory
> This is an incomplete outline implementation for a libblkio plugin for
> nbdkit. At the moment it only supports reading the same ("capacity")
> of the device, and not even reading or writing. I have some questions
> about the libblkio API before I can complete the plugin (see below).
>
> The
> This is upstream in nbdkit now:
> https://gitlab.com/nbdkit/nbdkit/-/tree/master/plugins/blkio
>
> Another question:
>
> (6) vhost-user + "read-only" property acts a bit strangely. After
> opening virtio-blk-vhost-user it throws an EROFS error if you try to
> "blkio_start" it. However if you
> (5) "The application is responsible for thread-safety. No thread
> synchronization is necessary when a queue is only used from a single
> thread. Proper synchronization is required when sharing a queue
> between multiple threads."
>
> Does this apply across multiple struct blkio handles? ie. Is
This is upstream in nbdkit now:
https://gitlab.com/nbdkit/nbdkit/-/tree/master/plugins/blkio
Another question:
(6) vhost-user + "read-only" property acts a bit strangely. After
opening virtio-blk-vhost-user it throws an EROFS error if you try to
"blkio_start" it. However if you set the
Here's an updated version which supports read, write, flush,
write-zeroes, discard and FUA:
https://gitlab.com/rwmjones/nbdkit/-/commits/2023-libblkio/
I was able to access a local file using the io_uring driver using
guestfish. You can try it like this:
$ ./nbdkit -fv blkio io_uring
On Wed, Jan 04, 2023 at 06:14:34PM +, Richard W.M. Jones wrote:
> (3) It seems like some drivers require pre-allocated memory regions,
> and since some do that means we might as well implement this. It
> also seems like some drivers require file-backed pre-allocated
> memory regions, and so
(5) "The application is responsible for thread-safety. No thread
synchronization is necessary when a queue is only used from a single
thread. Proper synchronization is required when sharing a queue
between multiple threads."
Does this apply across multiple struct blkio handles? ie. Is there
now,
On Wed, Jan 04, 2023 at 06:14:34PM +, Richard W.M. Jones wrote:
> This is an incomplete outline implementation for a libblkio plugin for
> nbdkit. At the moment it only supports reading the same ("capacity")
s/same/size/
--
Richard Jones, Virtualization Group, Red Hat
This is an incomplete outline implementation for a libblkio plugin for
nbdkit. At the moment it only supports reading the same ("capacity")
of the device, and not even reading or writing. I have some questions
about the libblkio API before I can complete the plugin (see below).
The idea here is
23 matches
Mail list logo
