Displaying 4 results from an estimated 4 matches for "addbuf".
Did you mean:
add_buf
2010 Jun 06
5
[PATCH] virtio_net: indicate oom when addbuf returns failure
On Fri, Jun 04, 2010 at 10:28:56AM +0930, Rusty Russell wrote:
> This patch is a subset of an already upstream patch, but this portion
> is useful in earlier releases.
>
> Please consider for the 2.6.32 and 2.6.33 stable trees.
>
> If the add_buf operation fails, indicate failure to the caller.
>
> Signed-off-by: Bruce Rogers <brogers at novell.com>
>
2010 Jun 06
5
[PATCH] virtio_net: indicate oom when addbuf returns failure
On Fri, Jun 04, 2010 at 10:28:56AM +0930, Rusty Russell wrote:
> This patch is a subset of an already upstream patch, but this portion
> is useful in earlier releases.
>
> Please consider for the 2.6.32 and 2.6.33 stable trees.
>
> If the add_buf operation fails, indicate failure to the caller.
>
> Signed-off-by: Bruce Rogers <brogers at novell.com>
>
2009 Jun 19
2
[PATCH/RFC] virtio_test: A module for testing virtio via userspace
...ys/bus/virtio/drivers/virtio_rng/unbind
$ modprobe virtio_test
On probe this module registers to all virtqueues and creates a character
device for every virtio device. (/dev/viotest<number>).
The character device offers ioctls to allow a userspace application to submit
virtio operations like addbuf, kick and getbuf. It also offers ioctls to get
information about the device and to query the amount of occurred callbacks (or
wait synchronously on callbacks).
The driver currently lacks the following planned features:
o userspace tooling for fuzzing (a prototype exists)
o feature bit support
o...
2009 Jun 19
2
[PATCH/RFC] virtio_test: A module for testing virtio via userspace
...ys/bus/virtio/drivers/virtio_rng/unbind
$ modprobe virtio_test
On probe this module registers to all virtqueues and creates a character
device for every virtio device. (/dev/viotest<number>).
The character device offers ioctls to allow a userspace application to submit
virtio operations like addbuf, kick and getbuf. It also offers ioctls to get
information about the device and to query the amount of occurred callbacks (or
wait synchronously on callbacks).
The driver currently lacks the following planned features:
o userspace tooling for fuzzing (a prototype exists)
o feature bit support
o...