Displaying 20 results from an estimated 3000 matches similar to: "[PATCH net v6] failover: allow name change on IFF_UP slave interfaces"
2019 Apr 09
0
[PATCH net v8] failover: allow name change on IFF_UP slave interfaces
On Mon, Apr 08, 2019 at 07:45:27PM -0400, Si-Wei Liu wrote:
> When a netdev appears through hot plug then gets enslaved by a failover
> master that is already up and running, the slave will be opened
> right away after getting enslaved. Today there's a race that userspace
> (udev) may fail to rename the slave if the kernel (net_failover)
> opens the slave earlier than when the
2019 Apr 08
0
[PATCH net v7] failover: allow name change on IFF_UP slave interfaces
On Mon, Apr 08, 2019 at 04:24:45PM -0400, Si-Wei Liu wrote:
> When a netdev appears through hot plug then gets enslaved by a failover
> master that is already up and running, the slave will be opened
> right away after getting enslaved. Today there's a race that userspace
> (udev) may fail to rename the slave if the kernel (net_failover)
> opens the slave earlier than when the
2019 Mar 07
0
[PATCH net v2] failover: allow name change on IFF_UP slave interfaces
On 3/6/2019 7:08 PM, Si-Wei Liu wrote:
> When a netdev appears through hot plug then gets enslaved by a failover
> master that is already up and running, the slave will be opened
> right away after getting enslaved. Today there's a race that userspace
> (udev) may fail to rename the slave if the kernel (net_failover)
> opens the slave earlier than when the userspace rename
2019 Mar 05
0
[RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
On Mon, Mar 04, 2019 at 07:50:59PM -0500, Si-Wei Liu wrote:
> When a netdev appears through hot plug then gets enslaved by a failover
> master that is already up and running, the slave will be opened
> right away after getting enslaved. Today there's a race that userspace
> (udev) may fail to rename the slave if the kernel (net_failover)
> opens the slave earlier than when the
2019 Mar 21
0
[PATCH net v2] failover: allow name change on IFF_UP slave interfaces
On 3/19/2019 10:20 PM, si-wei liu wrote:
> Hi Sridhar,
>
> Are you fine with leaving the IFF_SLAVE_RENAME_OK flag as is, and thus
> can provide your Ack-by or Reviewed-by? I can change the code if you
> feel strong.
My preference would be not to introduce a new flag unless there is any
usecase where we want a IFF_FAILOVER_SLAVE type of device to support 2
different behaviors.
2019 Mar 06
0
[RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
Tue, Mar 05, 2019 at 01:50:59AM CET, si-wei.liu at oracle.com wrote:
>When a netdev appears through hot plug then gets enslaved by a failover
>master that is already up and running, the slave will be opened
>right away after getting enslaved. Today there's a race that userspace
>(udev) may fail to rename the slave if the kernel (net_failover)
>opens the slave earlier than when
2019 Mar 21
0
[PATCH net v2] failover: allow name change on IFF_UP slave interfaces
> On 21 Mar 2019, at 16:04, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Wed, Mar 06, 2019 at 10:08:32PM -0500, Si-Wei Liu wrote:
>> When a netdev appears through hot plug then gets enslaved by a failover
>> master that is already up and running, the slave will be opened
>> right away after getting enslaved. Today there's a race that userspace
>>
2019 Mar 21
0
[PATCH net v2] failover: allow name change on IFF_UP slave interfaces
On Thu, Mar 21, 2019 at 04:20:40PM +0200, Liran Alon wrote:
>
>
> > On 21 Mar 2019, at 16:04, Michael S. Tsirkin <mst at redhat.com> wrote:
> >
> > On Wed, Mar 06, 2019 at 10:08:32PM -0500, Si-Wei Liu wrote:
> >> When a netdev appears through hot plug then gets enslaved by a failover
> >> master that is already up and running, the slave will be
2019 Mar 05
0
[RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
On Tue, Mar 05, 2019 at 11:19:32AM -0800, si-wei liu wrote:
>
>
> On 3/4/2019 6:33 PM, Michael S. Tsirkin wrote:
> > On Mon, Mar 04, 2019 at 07:50:59PM -0500, Si-Wei Liu wrote:
> > > When a netdev appears through hot plug then gets enslaved by a failover
> > > master that is already up and running, the slave will be opened
> > > right away after getting
2019 Mar 21
2
[PATCH net v2] failover: allow name change on IFF_UP slave interfaces
On Wed, Mar 06, 2019 at 10:08:32PM -0500, Si-Wei Liu wrote:
> When a netdev appears through hot plug then gets enslaved by a failover
> master that is already up and running, the slave will be opened
> right away after getting enslaved. Today there's a race that userspace
> (udev) may fail to rename the slave if the kernel (net_failover)
> opens the slave earlier than when the
2019 Mar 21
2
[PATCH net v2] failover: allow name change on IFF_UP slave interfaces
On Wed, Mar 06, 2019 at 10:08:32PM -0500, Si-Wei Liu wrote:
> When a netdev appears through hot plug then gets enslaved by a failover
> master that is already up and running, the slave will be opened
> right away after getting enslaved. Today there's a race that userspace
> (udev) may fail to rename the slave if the kernel (net_failover)
> opens the slave earlier than when the
2018 May 24
0
[PATCH net-next v12 1/5] net: Introduce generic failover module
The failover module provides a generic interface for paravirtual drivers
to register a netdev and a set of ops with a failover instance. The ops
are used as event handlers that get called to handle netdev register/
unregister/link change/name change events on slave pci ethernet devices
with the same mac address as the failover netdev.
This enables paravirtual drivers to use a VF as an accelerated
2018 May 07
0
[PATCH net-next v10 2/4] net: Introduce generic failover module
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.
It exposes 2 sets of interfaces to the paravirtual drivers.
1. For paravirtual drivers like virtio_net that use 3 netdev
2018 Apr 20
0
[PATCH v7 net-next 2/4] net: Introduce generic failover module
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.
It exposes 2 sets of interfaces to the paravirtual drivers.
1. existing netvsc driver that uses 2 netdev model. In this
2018 Apr 20
0
[PATCH v7 net-next 2/4] net: Introduce generic failover module
On 4/19/2018 7:44 PM, Michael S. Tsirkin wrote:
> On Thu, Apr 19, 2018 at 06:42:02PM -0700, Sridhar Samudrala 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
2018 Apr 20
2
[PATCH v7 net-next 2/4] net: Introduce generic failover module
On Thu, Apr 19, 2018 at 06:42:02PM -0700, Sridhar Samudrala 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.
>
> It exposes 2 sets of
2018 Apr 20
2
[PATCH v7 net-next 2/4] net: Introduce generic failover module
On Thu, Apr 19, 2018 at 06:42:02PM -0700, Sridhar Samudrala 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.
>
> It exposes 2 sets of
2018 May 22
0
[PATCH net-next v11 3/5] net: Introduce net_failover driver
The net_failover driver provides an automated failover mechanism via APIs
to create and destroy a failover master netdev and mananges a primary and
standby slave netdevs that get registered via the generic failover
infrastructure.
The failover netdev acts a master device and controls 2 slave devices. The
original paravirtual interface gets registered as 'standby' slave netdev and
a
2019 Apr 03
2
[PATCH net v5] failover: allow name change on IFF_UP slave interfaces
On Tue, 2 Apr 2019 15:23:29 -0700
si-wei liu <si-wei.liu at oracle.com> wrote:
> On 4/2/2019 2:53 PM, Stephen Hemminger wrote:
> > On Mon, 1 Apr 2019 19:04:53 -0400
> > Si-Wei Liu <si-wei.liu at oracle.com> wrote:
> >
> >> + if (dev->flags & IFF_UP &&
> >> + likely(!(dev->priv_flags & IFF_FAILOVER_SLAVE)))
> >
2019 Apr 03
2
[PATCH net v5] failover: allow name change on IFF_UP slave interfaces
On Tue, 2 Apr 2019 15:23:29 -0700
si-wei liu <si-wei.liu at oracle.com> wrote:
> On 4/2/2019 2:53 PM, Stephen Hemminger wrote:
> > On Mon, 1 Apr 2019 19:04:53 -0400
> > Si-Wei Liu <si-wei.liu at oracle.com> wrote:
> >
> >> + if (dev->flags & IFF_UP &&
> >> + likely(!(dev->priv_flags & IFF_FAILOVER_SLAVE)))
> >