thr3ads.net - search: "bond

[PATCH net-next] net: make ndo_get_stats64 a void function

2017 Jan 05

3

[PATCH net-next] net: make ndo_get_stats64 a void function

...e. Having a structure return value is potentially confusing because some future driver could incorrectly assume that the return value was used. Fix all drivers with ndo_get_stats64 to have a void function. Signed-off-by: Stephen Hemminger <sthemmin at microsoft.com> --- drivers/net/bonding/bond_main.c | 10 ++++------ drivers/net/dummy.c | 5 ++--- drivers/net/ethernet/alacritech/slicoss.c | 6 ++---- drivers/net/ethernet/amazon/ena/ena_netdev.c | 10 ++++------ drivers/net/ethernet/amd/xgbe/xgbe-drv.c | 6...

[PATCH net-next] net: make ndo_get_stats64 a void function

2017 Jan 05

3

[PATCH net-next] net: make ndo_get_stats64 a void function

...e. Having a structure return value is potentially confusing because some future driver could incorrectly assume that the return value was used. Fix all drivers with ndo_get_stats64 to have a void function. Signed-off-by: Stephen Hemminger <sthemmin at microsoft.com> --- drivers/net/bonding/bond_main.c | 10 ++++------ drivers/net/dummy.c | 5 ++--- drivers/net/ethernet/alacritech/slicoss.c | 6 ++---- drivers/net/ethernet/amazon/ena/ena_netdev.c | 10 ++++------ drivers/net/ethernet/amd/xgbe/xgbe-drv.c | 6...

[PATCH v7 net-next 2/4] net: Introduce generic failover module

2018 Apr 20

2

[PATCH v7 net-next 2/4] net: Introduce generic failover module

...ver.c b/net/core/failover.c > new file mode 100644 > index 000000000000..7bee762cb737 > --- /dev/null > +++ b/net/core/failover.c > @@ -0,0 +1,844 @@ > +// SPDX-License-Identifier: GPL-2.0 > +/* Copyright (c) 2018, Intel Corporation. */ I think you should copy the header from bond_main.c upon which some of the code seems to be based. > + > +/* A common module to handle registrations and notifications for paravirtual > + * drivers to enable accelerated datapath and support VF live migration. > + * > + * The notifier and event handling code is based on netvsc driver...

[PATCH v7 net-next 2/4] net: Introduce generic failover module

2018 Apr 20

2

[PATCH v7 net-next 2/4] net: Introduce generic failover module

...ver.c b/net/core/failover.c > new file mode 100644 > index 000000000000..7bee762cb737 > --- /dev/null > +++ b/net/core/failover.c > @@ -0,0 +1,844 @@ > +// SPDX-License-Identifier: GPL-2.0 > +/* Copyright (c) 2018, Intel Corporation. */ I think you should copy the header from bond_main.c upon which some of the code seems to be based. > + > +/* A common module to handle registrations and notifications for paravirtual > + * drivers to enable accelerated datapath and support VF live migration. > + * > + * The notifier and event handling code is based on netvsc driver...

[PATCH v7 net-next 2/4] net: Introduce generic failover module

2018 Apr 20

0

[PATCH v7 net-next 2/4] net: Introduce generic failover module

...new file mode 100644 >> index 000000000000..7bee762cb737 >> --- /dev/null >> +++ b/net/core/failover.c >> @@ -0,0 +1,844 @@ >> +// SPDX-License-Identifier: GPL-2.0 >> +/* Copyright (c) 2018, Intel Corporation. */ > > I think you should copy the header from bond_main.c upon which > some of the code seems to be based. Yes. some of the code is based on bonding/team and netvsc. i added a reference to netvsc in the comment, will also include bonding/team driver. > >> + >> +/* A common module to handle registrations and notifications for paravirt...

[Bridge] [PATCH 0/3] macvlan: add vepa and bridge mode

2009 Nov 17

11

[Bridge] [PATCH 0/3] macvlan: add vepa and bridge mode

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

[Bridge] [PATCH 0/3] macvlan: add vepa and bridge mode

2009 Nov 17

11

[Bridge] [PATCH 0/3] macvlan: add vepa and bridge mode

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

[Bridge] [PATCH 0/3] macvlan: add vepa and bridge mode

2009 Nov 17

11

[Bridge] [PATCH 0/3] macvlan: add vepa and bridge mode

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

[PATCH net-next v7 0/4] Enable virtio_net to act as a standby for a passthru device

2018 Apr 20

13

[PATCH net-next v7 0/4] Enable virtio_net to act as a standby 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_STANDBY that can be used

[PATCH -next 000/491] treewide: use fallthrough;

2020 Mar 11

0

[PATCH -next 000/491] treewide: use fallthrough;

[PATCH -next 000/491] treewide: use fallthrough;

2020 Mar 11

0

[PATCH -next 000/491] treewide: use fallthrough;

[PATCH -next 000/491] treewide: use fallthrough;

2020 Mar 11

0

[PATCH -next 000/491] treewide: use fallthrough;