search for: fleytman

From: Dmitry Fleytman <dfleytma at redhat.com> One of recently introduced Windows features (RSC) requires network driver to be able to enable and disable HW LRO offload on the fly without device reinitialization. Current Virtio specification doesn't support this requirement. The solution proposed by followin...

From: Dmitry Fleytman <dfleytma at redhat.com> One of recently introduced Windows features (RSC) requires network driver to be able to enable and disable HW LRO offload on the fly without device reinitialization. Current Virtio specification doesn't support this requirement. The solution proposed by followin...

From: Dmitry Fleytman <dfleytma at redhat.com> V2 changes: 1. _GUEST_ added to command and feature names 2. Live migration logic fixed Reported-by: Michael S. Tsirkin <mst at redhat.com> One of recently introduced Windows features (RSC) requires network driver to be able to enable and disable HW LRO o...

From: Dmitry Fleytman <dfleytma at redhat.com> V2 changes: 1. _GUEST_ added to command and feature names 2. Live migration logic fixed Reported-by: Michael S. Tsirkin <mst at redhat.com> One of recently introduced Windows features (RSC) requires network driver to be able to enable and disable HW LRO o...

From: Dmitry Fleytman <dfleytma at redhat.com> V4 changes: 1. Feature definitions re-used for command bitmask 2. Command data made uint64 3. Commit messsages fixed Reported-by: Rusty Russell rusty at rustcorp.com.au V3 changes: 1. Compat macro added 2. Feature name beautification V2 changes: 1. _GU...

From: Dmitry Fleytman <dfleytma at redhat.com> V4 changes: 1. Feature definitions re-used for command bitmask 2. Command data made uint64 3. Commit messsages fixed Reported-by: Rusty Russell rusty at rustcorp.com.au V3 changes: 1. Compat macro added 2. Feature name beautification V2 changes: 1. _GU...

From: Dmitry Fleytman <dfleytma at redhat.com> V3 changes: 1. Compat macro added 2. Feature name beautification V2 changes: 1. _GUEST_ added to command and feature names 2. Live migration logic fixed Reported-by: Michael S. Tsirkin <mst at redhat.com> One of recently introduced Windows features (...

From: Dmitry Fleytman <dfleytma at redhat.com> V3 changes: 1. Compat macro added 2. Feature name beautification V2 changes: 1. _GUEST_ added to command and feature names 2. Live migration logic fixed Reported-by: Michael S. Tsirkin <mst at redhat.com> One of recently introduced Windows features (...

...resting for QEMU because then we can use vhost as > a backend for other types of network adapters (like vmxnet3 or even > e1000). > > It also helps for things like fault tolerance where we need to be able > to control packet flow within QEMU. (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). Then I'm really confused as to what this would look like. A zero copy sendmsg? We should be able to implement that today. On the receive side, what can we do better than readv? If we need to return to userspace to tell the guest that we've got a new packet,...

...resting for QEMU because then we can use vhost as > a backend for other types of network adapters (like vmxnet3 or even > e1000). > > It also helps for things like fault tolerance where we need to be able > to control packet flow within QEMU. (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). Then I'm really confused as to what this would look like. A zero copy sendmsg? We should be able to implement that today. On the receive side, what can we do better than readv? If we need to return to userspace to tell the guest that we've got a new packet,...

...;> a backend for other types of network adapters (like vmxnet3 or even >>> e1000). >>> >>> It also helps for things like fault tolerance where we need to be able >>> to control packet flow within QEMU. >> >> (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). >> >> Then I'm really confused as to what this would look like. A zero copy >> sendmsg? We should be able to implement that today. >> >> On the receive side, what can we do better than readv? If we need to >> return to userspac...

...;> a backend for other types of network adapters (like vmxnet3 or even >>> e1000). >>> >>> It also helps for things like fault tolerance where we need to be able >>> to control packet flow within QEMU. >> >> (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). >> >> Then I'm really confused as to what this would look like. A zero copy >> sendmsg? We should be able to implement that today. >> >> On the receive side, what can we do better than readv? If we need to >> return to userspac...

...ike vmxnet3 or even >> >>> e1000). >> >>> >> >>> It also helps for things like fault tolerance where we need to be able >> >>> to control packet flow within QEMU. >> >> >> >> (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). >> >> >> >> Then I'm really confused as to what this would look like. A zero copy >> >> sendmsg? We should be able to implement that today. >> >> >> >> On the receive side, what can we do better than read...

...ike vmxnet3 or even >> >>> e1000). >> >>> >> >>> It also helps for things like fault tolerance where we need to be able >> >>> to control packet flow within QEMU. >> >> >> >> (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). >> >> >> >> Then I'm really confused as to what this would look like. A zero copy >> >> sendmsg? We should be able to implement that today. >> >> >> >> On the receive side, what can we do better than read...

...we can use vhost as >> a backend for other types of network adapters (like vmxnet3 or even >> e1000). >> >> It also helps for things like fault tolerance where we need to be able >> to control packet flow within QEMU. > > (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). > > Then I'm really confused as to what this would look like. A zero copy > sendmsg? We should be able to implement that today. > > On the receive side, what can we do better than readv? If we need to > return to userspace to tell the guest that...

...s of network adapters (like vmxnet3 or even > >>> e1000). > >>> > >>> It also helps for things like fault tolerance where we need to be able > >>> to control packet flow within QEMU. > >> > >> (CC's reduced, context added, Dmitry Fleytman added for vmxnet3 thoughts). > >> > >> Then I'm really confused as to what this would look like. A zero copy > >> sendmsg? We should be able to implement that today. > >> > >> On the receive side, what can we do better than readv? If we need to &g...

...ibson <david@gibson.dropbear.id.au> David Gibson <david@gibson.dropbear.id.au>`z David Holsgrove <david.holsgrove@xilinx.com> David Woodhouse <David.Woodhouse@intel.com> Dietmar Maurer <dietmar@proxmox.com> Dillon Amburgey <dillona@dillona.com> Dmitry Fleytman <dfleytma@redhat.com> Dmitry Fleytman <dmitry@daynix.com> Dominik Dingel <dingel@linux.vnet.ibm.com> Don Koch <dkoch@verizon.com> Dong Xu Wang <wdongxu@linux.vnet.ibm.com> Dongxue Zhang <elta.era@gmail.com> Doug Goldstein <cardoe@cardoe.com> D...

...ibson <david@gibson.dropbear.id.au> David Gibson <david@gibson.dropbear.id.au>`z David Holsgrove <david.holsgrove@xilinx.com> David Woodhouse <David.Woodhouse@intel.com> Dietmar Maurer <dietmar@proxmox.com> Dillon Amburgey <dillona@dillona.com> Dmitry Fleytman <dfleytma@redhat.com> Dmitry Fleytman <dmitry@daynix.com> Dominik Dingel <dingel@linux.vnet.ibm.com> Don Koch <dkoch@verizon.com> Dong Xu Wang <wdongxu@linux.vnet.ibm.com> Dongxue Zhang <elta.era@gmail.com> Doug Goldstein <cardoe@cardoe.com> D...

...ibson <david@gibson.dropbear.id.au> David Gibson <david@gibson.dropbear.id.au>`z David Holsgrove <david.holsgrove@xilinx.com> David Woodhouse <David.Woodhouse@intel.com> Dietmar Maurer <dietmar@proxmox.com> Dillon Amburgey <dillona@dillona.com> Dmitry Fleytman <dfleytma@redhat.com> Dmitry Fleytman <dmitry@daynix.com> Dominik Dingel <dingel@linux.vnet.ibm.com> Don Koch <dkoch@verizon.com> Dong Xu Wang <wdongxu@linux.vnet.ibm.com> Dongxue Zhang <elta.era@gmail.com> Doug Goldstein <cardoe@cardoe.com> D...

...-- 1 file changed, 258 insertions(+), 6 deletions(-) diff --git a/virtio-spec.lyx b/virtio-spec.lyx index 73e22e7..033362f 100644 --- a/virtio-spec.lyx +++ b/virtio-spec.lyx @@ -63,7 +63,7 @@ \author -385801441 "Cornelia Huck" cornelia.huck at de.ibm.com \author 460276516 "Dmitry Fleytman" dfleytma at redhat.com \author 1112500848 "Rusty Russell" rusty at rustcorp.com.au -\author 1531152142 "Paolo Bonzini,,," +\author 1531152142 "Paolo Bonzini" pbonzini at redhat.com \author 1717892615 "Alexey Zaytsev,,," \author 1986246365 "Mic...