search for: netdevic

Displaying 20 results from an estimated 1904 matches for "netdevic".

Did you mean: netdevice
2018 Apr 10
3
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
Tue, Apr 10, 2018 at 05:27:48PM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 8:22 AM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 05:13:40PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/10/2018 3:55 AM, Jiri Pirko wrote: >> > > Mon, Apr 09, 2018 at 08:47:06PM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/9/2018 1:07 AM,
2018 Apr 10
3
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
Tue, Apr 10, 2018 at 05:27:48PM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 8:22 AM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 05:13:40PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/10/2018 3:55 AM, Jiri Pirko wrote: >> > > Mon, Apr 09, 2018 at 08:47:06PM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/9/2018 1:07 AM,
2018 Apr 11
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
Tue, Apr 10, 2018 at 05:59:02PM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 8:43 AM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 05:27:48PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/10/2018 8:22 AM, Jiri Pirko wrote: >> > > Tue, Apr 10, 2018 at 05:13:40PM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/10/2018 3:55 AM,
2018 Apr 11
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
Tue, Apr 10, 2018 at 05:59:02PM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 8:43 AM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 05:27:48PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/10/2018 8:22 AM, Jiri Pirko wrote: >> > > Tue, Apr 10, 2018 at 05:13:40PM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/10/2018 3:55 AM,
2018 Apr 11
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
Wed, Apr 11, 2018 at 08:24:43AM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 11:03 PM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 05:59:02PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/10/2018 8:43 AM, Jiri Pirko wrote: >> > > Tue, Apr 10, 2018 at 05:27:48PM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/10/2018 8:22 AM,
2018 Apr 11
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
Wed, Apr 11, 2018 at 08:24:43AM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 11:03 PM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 05:59:02PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/10/2018 8:43 AM, Jiri Pirko wrote: >> > > Tue, Apr 10, 2018 at 05:27:48PM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/10/2018 8:22 AM,
2014 May 08
2
[PATCH] net: get rid of SET_ETHTOOL_OPS
...t;napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enet_ethtool_ops); + dev->ethtool_ops = &bcm_enet_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); ret = register_netdev(dev); @@ -2784,7 +2784,7 @@ static int bcm_enetsw_probe(struct platform_device *pdev) /* register netdevice */ dev->netdev_ops = &bcm_enetsw_ops; netif_napi_add(dev, &priv->napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enetsw_ethtool_ops); + dev->ethtool_ops = &bcm_enetsw_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); spin_lock_init(&priv->enetsw_m...
2014 May 08
2
[PATCH] net: get rid of SET_ETHTOOL_OPS
...t;napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enet_ethtool_ops); + dev->ethtool_ops = &bcm_enet_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); ret = register_netdev(dev); @@ -2784,7 +2784,7 @@ static int bcm_enetsw_probe(struct platform_device *pdev) /* register netdevice */ dev->netdev_ops = &bcm_enetsw_ops; netif_napi_add(dev, &priv->napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enetsw_ethtool_ops); + dev->ethtool_ops = &bcm_enetsw_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); spin_lock_init(&priv->enetsw_m...
2018 Apr 10
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
Tue, Apr 10, 2018 at 05:13:40PM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 3:55 AM, Jiri Pirko wrote: >> Mon, Apr 09, 2018 at 08:47:06PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/9/2018 1:07 AM, Jiri Pirko wrote: >> > > Sat, Apr 07, 2018 at 12:59:14AM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/6/2018 5:48 AM,
2018 Apr 10
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
Tue, Apr 10, 2018 at 05:13:40PM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 3:55 AM, Jiri Pirko wrote: >> Mon, Apr 09, 2018 at 08:47:06PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/9/2018 1:07 AM, Jiri Pirko wrote: >> > > Sat, Apr 07, 2018 at 12:59:14AM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/6/2018 5:48 AM,
2014 May 11
7
[PATCH] [resend] net: get rid of SET_ETHTOOL_OPS
...t;napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enet_ethtool_ops); + dev->ethtool_ops = &bcm_enet_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); ret = register_netdev(dev); @@ -2784,7 +2784,7 @@ static int bcm_enetsw_probe(struct platform_device *pdev) /* register netdevice */ dev->netdev_ops = &bcm_enetsw_ops; netif_napi_add(dev, &priv->napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enetsw_ethtool_ops); + dev->ethtool_ops = &bcm_enetsw_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); spin_lock_init(&priv->enetsw_m...
2014 May 11
7
[PATCH] [resend] net: get rid of SET_ETHTOOL_OPS
...t;napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enet_ethtool_ops); + dev->ethtool_ops = &bcm_enet_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); ret = register_netdev(dev); @@ -2784,7 +2784,7 @@ static int bcm_enetsw_probe(struct platform_device *pdev) /* register netdevice */ dev->netdev_ops = &bcm_enetsw_ops; netif_napi_add(dev, &priv->napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enetsw_ethtool_ops); + dev->ethtool_ops = &bcm_enetsw_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); spin_lock_init(&priv->enetsw_m...
2014 May 11
7
[PATCH] [resend] net: get rid of SET_ETHTOOL_OPS
...t;napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enet_ethtool_ops); + dev->ethtool_ops = &bcm_enet_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); ret = register_netdev(dev); @@ -2784,7 +2784,7 @@ static int bcm_enetsw_probe(struct platform_device *pdev) /* register netdevice */ dev->netdev_ops = &bcm_enetsw_ops; netif_napi_add(dev, &priv->napi, bcm_enet_poll, 16); - SET_ETHTOOL_OPS(dev, &bcm_enetsw_ethtool_ops); + dev->ethtool_ops = &bcm_enetsw_ethtool_ops; SET_NETDEV_DEV(dev, &pdev->dev); spin_lock_init(&priv->enetsw_m...
2018 May 07
1
[PATCH net-next v10 2/4] net: Introduce generic failover module
On Mon, 7 May 2018 15:10:44 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > This provides a generic interface for paravirtual drivers to listen > for netdev register/unregister/link change events from pci ethernet > devices with the same MAC and takeover their datapath. The notifier and > event handling code is based on the existing netvsc implementation. >
2014 May 11
0
[PATCH] [resend] net: get rid of SET_ETHTOOL_OPS
...&bcm_enet_ethtool_ops); > + dev->ethtool_ops = &bcm_enet_ethtool_ops; > SET_NETDEV_DEV(dev, &pdev->dev); > > ret = register_netdev(dev); > @@ -2784,7 +2784,7 @@ static int bcm_enetsw_probe(struct platform_device *pdev) > /* register netdevice */ > dev->netdev_ops = &bcm_enetsw_ops; > netif_napi_add(dev, &priv->napi, bcm_enet_poll, 16); > - SET_ETHTOOL_OPS(dev, &bcm_enetsw_ethtool_ops); > + dev->ethtool_ops = &bcm_enetsw_ethtool_ops; > SET_NETDEV_DEV(dev, &p...
2014 May 11
0
[PATCH] [resend] net: get rid of SET_ETHTOOL_OPS
...&bcm_enet_ethtool_ops); > + dev->ethtool_ops = &bcm_enet_ethtool_ops; > SET_NETDEV_DEV(dev, &pdev->dev); > > ret = register_netdev(dev); > @@ -2784,7 +2784,7 @@ static int bcm_enetsw_probe(struct platform_device *pdev) > /* register netdevice */ > dev->netdev_ops = &bcm_enetsw_ops; > netif_napi_add(dev, &priv->napi, bcm_enet_poll, 16); > - SET_ETHTOOL_OPS(dev, &bcm_enetsw_ethtool_ops); > + dev->ethtool_ops = &bcm_enetsw_ethtool_ops; > SET_NETDEV_DEV(dev, &p...
2014 May 08
0
[PATCH] net: get rid of SET_ETHTOOL_OPS
...&bcm_enet_ethtool_ops); > + dev->ethtool_ops = &bcm_enet_ethtool_ops; > SET_NETDEV_DEV(dev, &pdev->dev); > > ret = register_netdev(dev); > @@ -2784,7 +2784,7 @@ static int bcm_enetsw_probe(struct platform_device *pdev) > /* register netdevice */ > dev->netdev_ops = &bcm_enetsw_ops; > netif_napi_add(dev, &priv->napi, bcm_enet_poll, 16); > - SET_ETHTOOL_OPS(dev, &bcm_enetsw_ethtool_ops); > + dev->ethtool_ops = &bcm_enetsw_ethtool_ops; > SET_NETDEV_DEV(dev, &p...
2018 Feb 17
4
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
...ch might resolve the original issue. If I am reading things correctly what we end up with is the master showing up as "ens1" for example and the backup showing up as "ens1nbackup". Am I understanding that right? The problem with the team/bond%d approach is that it creates a new netdevice and so it would require guest configuration changes. > IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio > link is quite neat. I agree. For non-"backup" virio_net devices would it be okay for us to just return -EOPNOTSUPP? I assume it would be and tha...
2018 Feb 17
4
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
...ch might resolve the original issue. If I am reading things correctly what we end up with is the master showing up as "ens1" for example and the backup showing up as "ens1nbackup". Am I understanding that right? The problem with the team/bond%d approach is that it creates a new netdevice and so it would require guest configuration changes. > IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio > link is quite neat. I agree. For non-"backup" virio_net devices would it be okay for us to just return -EOPNOTSUPP? I assume it would be and tha...
2018 Apr 10
2
[RFC PATCH net-next v5 3/4] virtio_net: Extend virtio to use VF datapath when available
Mon, Apr 09, 2018 at 08:47:06PM CEST, sridhar.samudrala at intel.com wrote: >On 4/9/2018 1:07 AM, Jiri Pirko wrote: >> Sat, Apr 07, 2018 at 12:59:14AM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/6/2018 5:48 AM, Jiri Pirko wrote: >> > > Thu, Apr 05, 2018 at 11:08:22PM CEST, sridhar.samudrala at intel.com wrote: >> [...] >> >> > > >