similar to: virtio-user intarfece

Displaying 20 results from an estimated 10000 matches similar to: "virtio-user intarfece"

2018 Jan 09
2
[PATCH net-next] vhost_net: batch used ring update in rx
This patch tries to batched used ring update during RX. This is pretty fit for the case when guest is much faster (e.g dpdk based backend). In this case, used ring is almost empty: - we may get serious cache line misses/contending on both used ring and used idx. - at most 1 packet could be dequeued at one time, batching in guest does not make much effect. Update used ring in a batch can help
2023 Mar 13
1
[PATCH 1/2] vdpa/mlx5: Make VIRTIO_NET_F_MRG_RXBUF off by default
On Mon, Mar 13, 2023 at 09:14:38PM +0000, Parav Pandit wrote: > > > > From: Michael S. Tsirkin <mst at redhat.com> > > Sent: Sunday, March 12, 2023 12:24 PM > > > > On Sun, Mar 12, 2023 at 01:28:06PM +0000, Parav Pandit wrote: > > > > > > > > > > From: Michael S. Tsirkin <mst at redhat.com> > > > > Sent: Sunday,
2018 Apr 23
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, 23 Apr 2018 20:24:56 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > On Mon, Apr 23, 2018 at 10:04:06AM -0700, Stephen Hemminger wrote: > > > > > > > >I will NAK patches to change to common code for netvsc especially the > > > >three device model. MS worked hard with distro vendors to support transparent > > >
2018 Apr 23
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, 23 Apr 2018 20:24:56 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > On Mon, Apr 23, 2018 at 10:04:06AM -0700, Stephen Hemminger wrote: > > > > > > > >I will NAK patches to change to common code for netvsc especially the > > > >three device model. MS worked hard with distro vendors to support transparent > > >
2018 Apr 24
1
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, Apr 23, 2018 at 06:25:03PM -0700, Stephen Hemminger wrote: > On Mon, 23 Apr 2018 12:44:39 -0700 > Siwei Liu <loseweigh at gmail.com> wrote: > > > On Mon, Apr 23, 2018 at 10:56 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > > On Mon, Apr 23, 2018 at 10:44:40AM -0700, Stephen Hemminger wrote: > > >> On Mon, 23 Apr 2018 20:24:56 +0300
2018 Apr 23
5
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, Apr 23, 2018 at 10:56 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Mon, Apr 23, 2018 at 10:44:40AM -0700, Stephen Hemminger wrote: >> On Mon, 23 Apr 2018 20:24:56 +0300 >> "Michael S. Tsirkin" <mst at redhat.com> wrote: >> >> > On Mon, Apr 23, 2018 at 10:04:06AM -0700, Stephen Hemminger wrote: >> > > > >
2018 Apr 23
5
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, Apr 23, 2018 at 10:56 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Mon, Apr 23, 2018 at 10:44:40AM -0700, Stephen Hemminger wrote: >> On Mon, 23 Apr 2018 20:24:56 +0300 >> "Michael S. Tsirkin" <mst at redhat.com> wrote: >> >> > On Mon, Apr 23, 2018 at 10:04:06AM -0700, Stephen Hemminger wrote: >> > > > >
2016 Apr 18
1
Potential hang in virtnet_send_command
Hi, I was debugging an issue caused by a bad usage of dpdk. That is fixed in the meantime and I'll backport that into our code as well. But along debugging that, I found a potential hang in virtnet_send_command that my case ran into. The following code can become an infinite loop: /* Spin for a response, the kick causes an ioport write, trapping * into the hypervisor, so the request should
2016 Apr 18
1
Potential hang in virtnet_send_command
Hi, I was debugging an issue caused by a bad usage of dpdk. That is fixed in the meantime and I'll backport that into our code as well. But along debugging that, I found a potential hang in virtnet_send_command that my case ran into. The following code can become an infinite loop: /* Spin for a response, the kick causes an ioport write, trapping * into the hypervisor, so the request should
2018 Feb 22
3
"scripts are not supported on interfaces of type vhostuser" error
Hi, I'm having trouble starting a VM with vhostuser interfaces. I have a simple configuration where a VM running Debian has 1 vhostuser interface plugged into an OVS switch where a DPDK interface is already plugged in. $ ovs-vsctl show: Bridge "switch1" Port "switch1" Interface "switch1" type: internal Port "1.switch1"
2018 Apr 25
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, Apr 23, 2018 at 1:06 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Mon, Apr 23, 2018 at 12:44:39PM -0700, Siwei Liu wrote: >> On Mon, Apr 23, 2018 at 10:56 AM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Mon, Apr 23, 2018 at 10:44:40AM -0700, Stephen Hemminger wrote: >> >> On Mon, 23 Apr 2018 20:24:56 +0300 >> >>
2018 Apr 25
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, Apr 23, 2018 at 1:06 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Mon, Apr 23, 2018 at 12:44:39PM -0700, Siwei Liu wrote: >> On Mon, Apr 23, 2018 at 10:56 AM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Mon, Apr 23, 2018 at 10:44:40AM -0700, Stephen Hemminger wrote: >> >> On Mon, 23 Apr 2018 20:24:56 +0300 >> >>
2017 Nov 01
2
Virtio BoF minutes from KVM Forum 2017
On Wednesday, November 1, 2017 7:35 PM, Michael S. Tsirkin wrote: > > You have to either use and additional descriptor for metadata per chain. > > Or putting it in one of the buffers and forcing the lifetime of the metadata > and data to be the same. > > That's true. It would be easy to make descriptors e.g. 32 bytes each, so > you can add extra data in there. Or if we
2017 Nov 01
2
Virtio BoF minutes from KVM Forum 2017
On Wednesday, November 1, 2017 7:35 PM, Michael S. Tsirkin wrote: > > You have to either use and additional descriptor for metadata per chain. > > Or putting it in one of the buffers and forcing the lifetime of the metadata > and data to be the same. > > That's true. It would be easy to make descriptors e.g. 32 bytes each, so > you can add extra data in there. Or if we
2018 Apr 23
3
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Fri, 20 Apr 2018 18:00:58 +0200 Jiri Pirko <jiri at resnulli.us> wrote: > Fri, Apr 20, 2018 at 05:28:02PM CEST, stephen at networkplumber.org wrote: > >On Thu, 19 Apr 2018 18:42:04 -0700 > >Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > > > >> Use the registration/notification framework supported by the generic > >> failover
2018 Apr 23
3
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Fri, 20 Apr 2018 18:00:58 +0200 Jiri Pirko <jiri at resnulli.us> wrote: > Fri, Apr 20, 2018 at 05:28:02PM CEST, stephen at networkplumber.org wrote: > >On Thu, 19 Apr 2018 18:42:04 -0700 > >Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > > > >> Use the registration/notification framework supported by the generic > >> failover
2017 Mar 01
2
[virtio-dev] packed ring layout proposal - todo list
On Tue, Feb 28, 2017 at 12:29:43PM +0800, Yuanhan Liu wrote: > Hi Michael, > > Again, as usual, sorry for being late :/ > > On Wed, Feb 22, 2017 at 06:27:11AM +0200, Michael S. Tsirkin wrote: > > Stage 2: prototype guest/host drivers > > > > At this stage we need real guest and host drivers > > to be able to test real life performance. > > I suggest
2017 Mar 01
2
[virtio-dev] packed ring layout proposal - todo list
On Tue, Feb 28, 2017 at 12:29:43PM +0800, Yuanhan Liu wrote: > Hi Michael, > > Again, as usual, sorry for being late :/ > > On Wed, Feb 22, 2017 at 06:27:11AM +0200, Michael S. Tsirkin wrote: > > Stage 2: prototype guest/host drivers > > > > At this stage we need real guest and host drivers > > to be able to test real life performance. > > I suggest
2018 Apr 25
3
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Wed, Apr 25, 2018 at 3:22 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Wed, Apr 25, 2018 at 02:38:57PM -0700, Siwei Liu wrote: >> On Mon, Apr 23, 2018 at 1:06 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Mon, Apr 23, 2018 at 12:44:39PM -0700, Siwei Liu wrote: >> >> On Mon, Apr 23, 2018 at 10:56 AM, Michael S. Tsirkin <mst at
2018 Apr 25
3
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Wed, Apr 25, 2018 at 3:22 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Wed, Apr 25, 2018 at 02:38:57PM -0700, Siwei Liu wrote: >> On Mon, Apr 23, 2018 at 1:06 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Mon, Apr 23, 2018 at 12:44:39PM -0700, Siwei Liu wrote: >> >> On Mon, Apr 23, 2018 at 10:56 AM, Michael S. Tsirkin <mst at