From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v3 5/8] net/vdev_netvsc: implement core
	functionality
Date: Wed, 17 Jan 2018 17:51:45 +0100
Message-ID: <1755633.d9O1ru5VWe@xps>
References: <20171222173846.20731-1-adrien.mazarguil@6wind.com>
 <20180109104916.5919eebe@xeon-e3>
 <AM6PR0502MB3797D36A04BFB4D775D6259DD2110@AM6PR0502MB3797.eurprd05.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Matan Azrad <matan@mellanox.com>,
 Stephen Hemminger <stephen@networkplumber.org>,
 Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id E7AD21B020
 for <dev@dpdk.org>; Wed, 17 Jan 2018 17:52:18 +0100 (CET)
In-Reply-To: <AM6PR0502MB3797D36A04BFB4D775D6259DD2110@AM6PR0502MB3797.eurprd05.prod.outlook.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

10/01/2018 16:02, Matan Azrad:
> From: Stephen Hemminger, Tuesday, January 9, 2018 8:49 PM
> > On Tue,  9 Jan 2018 14:47:30 +0000
> > Matan Azrad <matan@mellanox.com> wrote:
> > > +	ret = rte_eal_alarm_set(VDEV_NETVSC_PROBE_MS * 1000,
> > > +				vdev_netvsc_alarm, NULL);
> > > +	if (ret < 0) {
> > > +		DRV_LOG(ERR, "unable to reschedule alarm callback: %s",
> > > +			rte_strerror(-ret));
> > > +	}
> > > +}
> > 
> > Why not use netlink uevent?
> 
> As described in doc, we can improve the hotplug mechanism(here and in fail-safe) after EAL hotplug work will be done.
> So, maybe in next release we will change it to use uevent by EAL hotplug.

I don't see any progress here for one week.
Yes it is a temporary solution waiting for hotplug event callback in EAL.
Hopefully it will be possible to do such improvements in 18.05.

Am I missing something else?
Or can it be applied to next-net?