search for: detach_outbuf

...the size of the sg array. + * used: the length sent (set once data received). + * Returns an identifier or an error (eg. -ENOSPC). + * @sync: update after add_inbuf/add_outbuf + * vdev: the virtio_device we're talking about. + * Use the virtio_sync wrapper, to avoid unnecessary calls. + * @detach_outbuf: make sure sent sg can no longer be read. + * vdev: the virtio_device we're talking about. + * id: the identifier returned from add_outbuf. + * @detach_inbuf: make sure sent sg can no longer be written to. + * vdev: the virtio_device we're talking about. + * id: the identifier returned from...

...the size of the sg array. + * used: the length sent (set once data received). + * Returns an identifier or an error (eg. -ENOSPC). + * @sync: update after add_inbuf/add_outbuf + * vdev: the virtio_device we're talking about. + * Use the virtio_sync wrapper, to avoid unnecessary calls. + * @detach_outbuf: make sure sent sg can no longer be read. + * vdev: the virtio_device we're talking about. + * id: the identifier returned from add_outbuf. + * @detach_inbuf: make sure sent sg can no longer be written to. + * vdev: the virtio_device we're talking about. + * id: the identifier returned from...

...the size of the sg array. + * used: the length sent (set once data received). + * Returns an identifier or an error (eg. -ENOSPC). + * @sync: update after add_inbuf/add_outbuf + * vdev: the virtio_device we're talking about. + * Use the virtio_sync wrapper, to avoid unnecessary calls. + * @detach_outbuf: make sure sent sg can no longer be read. + * vdev: the virtio_device we're talking about. + * id: the identifier returned from add_outbuf. + * @detach_inbuf: make sure sent sg can no longer be written to. + * vdev: the virtio_device we're talking about. + * id: the identifier returned from...

Hi again all, It turns out that networking really wants ordered requests, which the previous patches didn't allow. This patch changes it to a callback mechanism; kudos to Avi. The downside is that locking is more complicated, and after a few dead ends I implemented the simplest solution: the struct virtio_device contains the spinlock to use, and it's held when your callbacks get

Hi again all, It turns out that networking really wants ordered requests, which the previous patches didn't allow. This patch changes it to a callback mechanism; kudos to Avi. The downside is that locking is more complicated, and after a few dead ends I implemented the simplest solution: the struct virtio_device contains the spinlock to use, and it's held when your callbacks get

Hi again all, It turns out that networking really wants ordered requests, which the previous patches didn't allow. This patch changes it to a callback mechanism; kudos to Avi. The downside is that locking is more complicated, and after a few dead ends I implemented the simplest solution: the struct virtio_device contains the spinlock to use, and it's held when your callbacks get

This is a subject that came up in the virtio BOF session at OLS. I decided to go forward and implement something that I like, based on the latest virtio proposal at the time, which was draft III. It's not a drop-in replacement, because it's missing a host implementation. I first started my own, which is not done yet, but wanted to do one for lguest and one for emulated PCI next. It's

This is a subject that came up in the virtio BOF session at OLS. I decided to go forward and implement something that I like, based on the latest virtio proposal at the time, which was draft III. It's not a drop-in replacement, because it's missing a host implementation. I first started my own, which is not done yet, but wanted to do one for lguest and one for emulated PCI next. It's