[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180408.123207.2294740686493951200.davem@davemloft.net>
Date: Sun, 08 Apr 2018 12:32:07 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: loseweigh@...il.com
Cc: dsahern@...il.com, jiri@...nulli.us, si-wei.liu@...cle.com,
mst@...hat.com, stephen@...workplumber.org,
alexander.h.duyck@...el.com, jesse.brandeburg@...el.com,
kubakici@...pl, jasowang@...hat.com, sridhar.samudrala@...el.com,
netdev@...r.kernel.org, virtualization@...ts.linux-foundation.org,
virtio-dev@...ts.oasis-open.org
Subject: Re: [RFC PATCH 2/3] netdev: kernel-only IFF_HIDDEN netdevice
From: Siwei Liu <loseweigh@...il.com>
Date: Fri, 6 Apr 2018 19:32:05 -0700
> And I assume everyone here understands the use case for live
> migration (in the context of providing cloud service) is very
> different, and we have to hide the netdevs. If not, I'm more than
> happy to clarify.
I think you still need to clarify.
netdevs are netdevs. If they have special attributes, mark them as
such and the tools base their actions upon that.
"Hiding", or changing classes, doesn't make any sense to me still.
Powered by blists - more mailing lists