similar to: virtio message framing

Displaying 20 results from an estimated 50000 matches similar to: "virtio message framing"

2013 Jun 19
3
[PATCH] virtio-spec: add field for scsi command size
"Michael S. Tsirkin" <mst at redhat.com> writes: > On Thu, Jun 13, 2013 at 11:10:47AM +0300, Michael S. Tsirkin wrote: >> On Thu, Jun 13, 2013 at 11:02:59AM +0300, Michael S. Tsirkin wrote: >> > On Thu, Jun 13, 2013 at 02:12:22PM +0930, Rusty Russell wrote: >> > > "Michael S. Tsirkin" <mst at redhat.com> writes: >> > > >
2013 Jun 19
3
[PATCH] virtio-spec: add field for scsi command size
"Michael S. Tsirkin" <mst at redhat.com> writes: > On Thu, Jun 13, 2013 at 11:10:47AM +0300, Michael S. Tsirkin wrote: >> On Thu, Jun 13, 2013 at 11:02:59AM +0300, Michael S. Tsirkin wrote: >> > On Thu, Jun 13, 2013 at 02:12:22PM +0930, Rusty Russell wrote: >> > > "Michael S. Tsirkin" <mst at redhat.com> writes: >> > > >
2013 Jul 04
2
[PATCH] virtio-spec: add field for scsi command size
On Tue, Jul 02, 2013 at 03:34:09PM +0930, Rusty Russell wrote: > Paolo Bonzini <pbonzini at redhat.com> writes: > > Il 01/07/2013 01:47, Rusty Russell ha scritto: > >> > > > >> > > Mainly because I'm not sure that *all* devices are now safe. Are they? > >> > > >> > virtio-scsi's implementation in QEMU is not safe (been
2013 Jul 04
2
[PATCH] virtio-spec: add field for scsi command size
On Tue, Jul 02, 2013 at 03:34:09PM +0930, Rusty Russell wrote: > Paolo Bonzini <pbonzini at redhat.com> writes: > > Il 01/07/2013 01:47, Rusty Russell ha scritto: > >> > > > >> > > Mainly because I'm not sure that *all* devices are now safe. Are they? > >> > > >> > virtio-scsi's implementation in QEMU is not safe (been
2009 Sep 09
1
[PATCH] SCSI driver for VMware's virtual HBA - V4.
Hi Alok, Joining this a bit late as this was just brought to my attention. It would have been nice to CC the virtualization mailing list. Please do in future submissions. Alok Kataria wrote: > VMware PVSCSI driver - v4. > / > > diff --git a/drivers/scsi/pvscsi.h b/drivers/scsi/pvscsi.h > new file mode 100644 > index 0000000..96bb655 > --- /dev/null > +++
2009 Sep 09
1
[PATCH] SCSI driver for VMware's virtual HBA - V4.
Hi Alok, Joining this a bit late as this was just brought to my attention. It would have been nice to CC the virtualization mailing list. Please do in future submissions. Alok Kataria wrote: > VMware PVSCSI driver - v4. > / > > diff --git a/drivers/scsi/pvscsi.h b/drivers/scsi/pvscsi.h > new file mode 100644 > index 0000000..96bb655 > --- /dev/null > +++
2017 Sep 25
2
[virtio-dev] packed ring layout proposal v3
On Wed, Sep 20, 2017 at 09:11:57AM +0000, Liang, Cunming wrote: > Hi Michael, > > > -----Original Message----- > > From: virtio-dev at lists.oasis-open.org [mailto:virtio-dev at lists.oasis-open.org] > > On Behalf Of Michael S. Tsirkin > > Sent: Sunday, September 10, 2017 1:06 PM > > To: virtio-dev at lists.oasis-open.org > > Cc: virtualization at
2017 Sep 25
2
[virtio-dev] packed ring layout proposal v3
On Wed, Sep 20, 2017 at 09:11:57AM +0000, Liang, Cunming wrote: > Hi Michael, > > > -----Original Message----- > > From: virtio-dev at lists.oasis-open.org [mailto:virtio-dev at lists.oasis-open.org] > > On Behalf Of Michael S. Tsirkin > > Sent: Sunday, September 10, 2017 1:06 PM > > To: virtio-dev at lists.oasis-open.org > > Cc: virtualization at
2014 Oct 11
2
[PATCH net-next RFC 1/3] virtio: support for urgent descriptors
Below should be useful for some experiments Jason is doing. I thought I'd send it out for early review/feedback. event idx feature allows us to defer interrupts until a specific # of descriptors were used. Sometimes it might be useful to get an interrupt after a specific descriptor, regardless. This adds a descriptor flag for this, and an API to create an urgent output descriptor. This is
2014 Oct 11
2
[PATCH net-next RFC 1/3] virtio: support for urgent descriptors
Below should be useful for some experiments Jason is doing. I thought I'd send it out for early review/feedback. event idx feature allows us to defer interrupts until a specific # of descriptors were used. Sometimes it might be useful to get an interrupt after a specific descriptor, regardless. This adds a descriptor flag for this, and an API to create an urgent output descriptor. This is
2015 Sep 09
2
virtio optimization idea
On Fri, Sep 04, 2015 at 08:25:05AM +0000, Xie, Huawei wrote: > Hi: > > Recently I have done one virtio optimization proof of concept. The > optimization includes two parts: > 1) avail ring set with fixed descriptors > 2) RX vectorization > With the optimizations, we could have several times of performance boost > for purely vhost-virtio throughput. Thanks! I'm very
2015 Sep 09
2
virtio optimization idea
On Fri, Sep 04, 2015 at 08:25:05AM +0000, Xie, Huawei wrote: > Hi: > > Recently I have done one virtio optimization proof of concept. The > optimization includes two parts: > 1) avail ring set with fixed descriptors > 2) RX vectorization > With the optimizations, we could have several times of performance boost > for purely vhost-virtio throughput. Thanks! I'm very
2008 Apr 05
11
[PATCH RFC 1/5] vringfd syscall
For virtualization, we've developed virtio_ring for efficient communication. This would also work well for userspace-kernel communication, particularly for things like the tun device. By using the same ABI, we can join guests to the host kernel trivially. These patches are fairly alpha; I've seen some network stalls I have to track down and there are some fixmes. Comments welcome!
2008 Apr 05
11
[PATCH RFC 1/5] vringfd syscall
For virtualization, we've developed virtio_ring for efficient communication. This would also work well for userspace-kernel communication, particularly for things like the tun device. By using the same ABI, we can join guests to the host kernel trivially. These patches are fairly alpha; I've seen some network stalls I have to track down and there are some fixmes. Comments welcome!
2013 Jun 13
2
[PATCH] virtio-spec: add field for scsi command size
On Thu, Jun 13, 2013 at 11:02:59AM +0300, Michael S. Tsirkin wrote: > On Thu, Jun 13, 2013 at 02:12:22PM +0930, Rusty Russell wrote: > > "Michael S. Tsirkin" <mst at redhat.com> writes: > > > On Thu, Mar 14, 2013 at 04:15:28PM +0100, Paolo Bonzini wrote: > > >> Il 14/03/2013 12:10, Michael S. Tsirkin ha scritto: > > >> > Add field for
2013 Jun 13
2
[PATCH] virtio-spec: add field for scsi command size
On Thu, Jun 13, 2013 at 11:02:59AM +0300, Michael S. Tsirkin wrote: > On Thu, Jun 13, 2013 at 02:12:22PM +0930, Rusty Russell wrote: > > "Michael S. Tsirkin" <mst at redhat.com> writes: > > > On Thu, Mar 14, 2013 at 04:15:28PM +0100, Paolo Bonzini wrote: > > >> Il 14/03/2013 12:10, Michael S. Tsirkin ha scritto: > > >> > Add field for
2018 Apr 23
2
[RFC v2] virtio: support packed ring
On Mon, Apr 23, 2018 at 01:42:14PM +0800, Jason Wang wrote: > On 2018?04?01? 22:12, Tiwei Bie wrote: > > Hello everyone, > > > > This RFC implements packed ring support for virtio driver. > > > > The code was tested with DPDK vhost (testpmd/vhost-PMD) implemented > > by Jens at http://dpdk.org/ml/archives/dev/2018-January/089417.html > > Minor changes
2018 Apr 23
2
[RFC v2] virtio: support packed ring
On Mon, Apr 23, 2018 at 01:42:14PM +0800, Jason Wang wrote: > On 2018?04?01? 22:12, Tiwei Bie wrote: > > Hello everyone, > > > > This RFC implements packed ring support for virtio driver. > > > > The code was tested with DPDK vhost (testpmd/vhost-PMD) implemented > > by Jens at http://dpdk.org/ml/archives/dev/2018-January/089417.html > > Minor changes
2024 Nov 01
1
NUT 2.8.1-3 " Can't claim USB device [051d:0002]@0/0: Entity not found" using usbhid-ups
Hi Jim, Thanks for your help. I'll respond in the same order as you did: 1. Unfortunately, I did "chown" stuff to these created users... Since the other three responses don't seem to be what you're looking for (but that's only my uninformed interpretation), I suppose the problem lies here? Is there a number of files/directories that I should
2024 Nov 01
1
NUT 2.8.1-3 " Can't claim USB device [051d:0002]@0/0: Entity not found" using usbhid-ups
Hello, I was thinking about what could be going wrong here, and a few ideas pop up: 1) If you installed NUT from packaging, there should have been no need to add OS groups/users manually. There is a valid use-case for running different daemons under different accounts, as long as they talk over network and access same files or UNIX sockets at best by sharing a group for that, but it does need