search for: bypass_master

Displaying 20 results from an estimated 38 matches for "bypass_master".

2018 Apr 11
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...tation. > >It exposes 2 sets of interfaces to the paravirtual drivers. >1. existing netvsc driver that uses 2 netdev model. In this model, no >master netdev is created. The paravirtual driver registers each bypass >instance along with a set of ops to manage the slave events. > bypass_master_register() > bypass_master_unregister() >2. new virtio_net based solution that uses 3 netdev model. In this model, >the bypass module provides interfaces to create/destroy additional master >netdev and all the slave events are managed internally. > bypass_master_create()...
2018 Apr 11
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...tation. > >It exposes 2 sets of interfaces to the paravirtual drivers. >1. existing netvsc driver that uses 2 netdev model. In this model, no >master netdev is created. The paravirtual driver registers each bypass >instance along with a set of ops to manage the slave events. > bypass_master_register() > bypass_master_unregister() >2. new virtio_net based solution that uses 3 netdev model. In this model, >the bypass module provides interfaces to create/destroy additional master >netdev and all the slave events are managed internally. > bypass_master_create()...
2018 Apr 10
0
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...existing netvsc implementation. It exposes 2 sets of interfaces to the paravirtual drivers. 1. existing netvsc driver that uses 2 netdev model. In this model, no master netdev is created. The paravirtual driver registers each bypass instance along with a set of ops to manage the slave events. bypass_master_register() bypass_master_unregister() 2. new virtio_net based solution that uses 3 netdev model. In this model, the bypass module provides interfaces to create/destroy additional master netdev and all the slave events are managed internally. bypass_master_create() bypass_master...
2018 Apr 11
0
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...exposes 2 sets of interfaces to the paravirtual drivers. >> 1. existing netvsc driver that uses 2 netdev model. In this model, no >> master netdev is created. The paravirtual driver registers each bypass >> instance along with a set of ops to manage the slave events. >> bypass_master_register() >> bypass_master_unregister() >> 2. new virtio_net based solution that uses 3 netdev model. In this model, >> the bypass module provides interfaces to create/destroy additional master >> netdev and all the slave events are managed internally. >>...
2018 Apr 10
6
[RFC PATCH net-next v6 0/4] Enable virtio_net to act as a backup for a passthru device
The main motivation for this patch is to enable cloud service providers to provide an accelerated datapath to virtio-net enabled VMs in a transparent manner with no/minimal guest userspace changes. This also enables hypervisor controlled live migration to be supported with VMs that have direct attached SR-IOV VF devices. Patch 1 introduces a new feature bit VIRTIO_NET_F_BACKUP that can be
2018 Apr 09
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...bypass module to indicate if the driver is doing >a 2 netdev or 3 netdev model and based on that flag this check can be done in bypass module >for 3 netdev scenario. Just let me undestand it clearly. What I expect the difference would be between 2netdev and3 netdev model is this: 2netdev: bypass_master / / VF_slave 3netdev: bypass_master / \ / \ VF_slave backup_slave Is that correct? If not, how does it look like? Thanks!
2018 Apr 09
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...bypass module to indicate if the driver is doing >a 2 netdev or 3 netdev model and based on that flag this check can be done in bypass module >for 3 netdev scenario. Just let me undestand it clearly. What I expect the difference would be between 2netdev and3 netdev model is this: 2netdev: bypass_master / / VF_slave 3netdev: bypass_master / \ / \ VF_slave backup_slave Is that correct? If not, how does it look like? Thanks!
2018 Apr 09
0
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...the driver is doing >> a 2 netdev or 3 netdev model and based on that flag this check can be done in bypass module >> for 3 netdev scenario. > Just let me undestand it clearly. What I expect the difference would be > between 2netdev and3 netdev model is this: > 2netdev: > bypass_master > / > / > VF_slave > > 3netdev: > bypass_master > / \ > / \ > VF_slave backup_slave > > Is that correct? If not, how does it look like? > > Looks correct. VF_slave and backup_slave are the original netdevs a...
2018 Apr 18
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...terfaces to the paravirtual drivers. >> > 1. existing netvsc driver that uses 2 netdev model. In this model, no >> > master netdev is created. The paravirtual driver registers each bypass >> > instance along with a set of ops to manage the slave events. >> > bypass_master_register() >> > bypass_master_unregister() >> > 2. new virtio_net based solution that uses 3 netdev model. In this model, >> > the bypass module provides interfaces to create/destroy additional master >> > netdev and all the slave events are managed inte...
2018 Apr 18
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...terfaces to the paravirtual drivers. >> > 1. existing netvsc driver that uses 2 netdev model. In this model, no >> > master netdev is created. The paravirtual driver registers each bypass >> > instance along with a set of ops to manage the slave events. >> > bypass_master_register() >> > bypass_master_unregister() >> > 2. new virtio_net based solution that uses 3 netdev model. In this model, >> > the bypass module provides interfaces to create/destroy additional master >> > netdev and all the slave events are managed inte...
2018 Apr 10
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...t; > a 2 netdev or 3 netdev model and based on that flag this check can be done in bypass module >> > for 3 netdev scenario. >> Just let me undestand it clearly. What I expect the difference would be >> between 2netdev and3 netdev model is this: >> 2netdev: >> bypass_master >> / >> / >> VF_slave >> >> 3netdev: >> bypass_master >> / \ >> / \ >> VF_slave backup_slave >> >> Is that correct? If not, how does it look like? >> >> >Looks c...
2018 Apr 10
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...t; > a 2 netdev or 3 netdev model and based on that flag this check can be done in bypass module >> > for 3 netdev scenario. >> Just let me undestand it clearly. What I expect the difference would be >> between 2netdev and3 netdev model is this: >> 2netdev: >> bypass_master >> / >> / >> VF_slave >> >> 3netdev: >> bypass_master >> / \ >> / \ >> VF_slave backup_slave >> >> Is that correct? If not, how does it look like? >> >> >Looks c...
2018 Apr 11
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...; > > > > Just let me undestand it clearly. What I expect the difference would be >> > > > > > > > > between 2netdev and3 netdev model is this: >> > > > > > > > > 2netdev: >> > > > > > > > > bypass_master >> > > > > > > > > / >> > > > > > > > > / >> > > > > > > > > VF_slave >> > > > > > > > > >> > > > > > > > > 3netdev: >...
2018 Apr 11
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...; > > > > Just let me undestand it clearly. What I expect the difference would be >> > > > > > > > > between 2netdev and3 netdev model is this: >> > > > > > > > > 2netdev: >> > > > > > > > > bypass_master >> > > > > > > > > / >> > > > > > > > > / >> > > > > > > > > VF_slave >> > > > > > > > > >> > > > > > > > > 3netdev: >...
2018 Apr 10
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...hat flag this check can be done in bypass module >> > > > for 3 netdev scenario. >> > > Just let me undestand it clearly. What I expect the difference would be >> > > between 2netdev and3 netdev model is this: >> > > 2netdev: >> > > bypass_master >> > > / >> > > / >> > > VF_slave >> > > >> > > 3netdev: >> > > bypass_master >> > > / \ >> > > / \ >> > > VF_slave backup_slave &gt...
2018 Apr 10
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...hat flag this check can be done in bypass module >> > > > for 3 netdev scenario. >> > > Just let me undestand it clearly. What I expect the difference would be >> > > between 2netdev and3 netdev model is this: >> > > 2netdev: >> > > bypass_master >> > > / >> > > / >> > > VF_slave >> > > >> > > 3netdev: >> > > bypass_master >> > > / \ >> > > / \ >> > > VF_slave backup_slave &gt...
2018 Apr 10
3
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...t;> > > > > > for 3 netdev scenario. >> > > > > Just let me undestand it clearly. What I expect the difference would be >> > > > > between 2netdev and3 netdev model is this: >> > > > > 2netdev: >> > > > > bypass_master >> > > > > / >> > > > > / >> > > > > VF_slave >> > > > > >> > > > > 3netdev: >> > > > > bypass_master >> > > > > / \ >> &g...
2018 Apr 10
3
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
...t;> > > > > > for 3 netdev scenario. >> > > > > Just let me undestand it clearly. What I expect the difference would be >> > > > > between 2netdev and3 netdev model is this: >> > > > > 2netdev: >> > > > > bypass_master >> > > > > / >> > > > > / >> > > > > VF_slave >> > > > > >> > > > > 3netdev: >> > > > > bypass_master >> > > > > / \ >> &g...
2018 Apr 18
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...> > > > 1. existing netvsc driver that uses 2 netdev model. In this model, no >> > > > master netdev is created. The paravirtual driver registers each bypass >> > > > instance along with a set of ops to manage the slave events. >> > > > bypass_master_register() >> > > > bypass_master_unregister() >> > > > 2. new virtio_net based solution that uses 3 netdev model. In this model, >> > > > the bypass module provides interfaces to create/destroy additional master >> > > > netdev...
2018 Apr 18
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...> > > > 1. existing netvsc driver that uses 2 netdev model. In this model, no >> > > > master netdev is created. The paravirtual driver registers each bypass >> > > > instance along with a set of ops to manage the slave events. >> > > > bypass_master_register() >> > > > bypass_master_unregister() >> > > > 2. new virtio_net based solution that uses 3 netdev model. In this model, >> > > > the bypass module provides interfaces to create/destroy additional master >> > > > netdev...