netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, sthemmin@microsoft.com
Subject: Re: [PATCH] hv_netvsc: update VF after name has changed.
Date: Tue, 26 Dec 2017 13:51:43 -0800	[thread overview]
Message-ID: <20171226135143.639c8476@xeon-e3> (raw)
In-Reply-To: <20171226.122512.2094828192772967433.davem@davemloft.net>

On Tue, 26 Dec 2017 12:25:12 -0500 (EST)
David Miller <davem@davemloft.net> wrote:

> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Wed, 20 Dec 2017 14:33:23 -0800
> 
> > Since commit 6123c66854c1 ("netvsc: delay setup of VF device")
> > the automatic bring up of the VF is delayed to allow userspace (udev)
> > a chance to rename the device. This delay is problematic because
> > it delays boot and may not be long enough for some cases.
> > 
> > Instead, use the rename can be used to trigger the next step
> > in setup to happen immediately.
> > 
> > The VF initialization sequence now looks like:
> >    * hotplug causes VF network device probe to create network device
> >    * netvsc notifier joins VF with netvsc and schedules VF to be
> >      setup after timer expires
> >    * udev in userspace renames device
> >    * if netvsc notifier detects rename, it can cancel timer
> >      and do immediate setup
> > 
> > The delay can also be increased to allow for slower rules.
> > Still need the delayed work to handle the case where rename is
> > not done.
> > 
> > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>  
> 
> I'm still seriously perplexed by this whole situation.

See state diagram below
 
> Why can't you bring up a VF interface simply because of a text string
> used to reffered to it?

VF network device can not have its name changed if up.
The network device kernel API does not allow name change of network
device that is up.  There was a patch from Vitaly to allow this, but it
was deemed to be too risky.

   https://patchwork.ozlabs.org/patch/799646/

> If the VF interface were named "rabbit" I don't see why it can't be
> brought up until it is named "tiger"
> 
> I'm not applying any patches in this area until we have a better
> understanding of what the real issue is, and have a real solution
> that can be applied to any other VF interface implemented in the
> tree.

                       Netvsc                  VF Network
                       Device                  Device

                         |                       |
                         |                       |
udev network daemon      |                       +<------------- PCI hotplug
                         |    NETDEV_REGISTER    |
     +                   +<----------------------+ register_netdev
     |                                           |
     |                   |                       |
     |                   +---------------------->+
     |                   |  netdev_rx_handler    |
     |                   |                       |
     |                   +---------------------> |
     |                   | netdev_upper_dev_link |
     +<------------------+                       |
     |  udev device add  |                       |
     |                   |                       |
     |                   |                       |
     |                   |                       |
     +-------------------+---------------------> |
     |     rename eth1 to enp12s0                |
     |                   |     NETDEV_CHANGENAME |
     |                   <-----------------------+
     |                   |                       |
     |                   |                       |
     |                   +---------------------> |
     |                   |   dev_set_mtu         |
     |                   |                       |
     |                   +---------------------> |
     |                   |   dev_open            |
     |                   |                       |
     |                   |    NETDEV_UP          |
     |                   <-----------------------+
     v                   |                       |
                         |                       |
                         |                       |
                         +----------------------------------> Hyper-V host
                         |        RNDIS switch datapath
                         |                       |
                         v                       v

  reply	other threads:[~2017-12-26 21:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 22:33 [PATCH] hv_netvsc: update VF after name has changed Stephen Hemminger
2017-12-26 17:25 ` David Miller
2017-12-26 21:51   ` Stephen Hemminger [this message]
2017-12-26 22:11     ` David Miller
2017-12-26 23:46       ` Stephen Hemminger
2018-01-25 19:19       ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171226135143.639c8476@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sthemmin@microsoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).