From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v4 04/12] net/failsafe: add fail-safe PMD Date: Thu, 1 Jun 2017 10:57:22 -0700 Message-ID: <20170601105722.6e4e2101@xeon-e3> References: <22f681327bdff42db58d880fd2238d1fbfb2730d.1496065002.git.gaetan.rivet@6wind.com> <20170531081353.2103a676@xeon-e3> <20170601140137.GB18840@bidouze.vm.6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org To: =?UTF-8?B?R2HDq3Rhbg==?= Rivet Return-path: Received: from mail-pf0-f181.google.com (mail-pf0-f181.google.com [209.85.192.181]) by dpdk.org (Postfix) with ESMTP id 8CF637CCE for ; Thu, 1 Jun 2017 19:57:32 +0200 (CEST) Received: by mail-pf0-f181.google.com with SMTP id 9so33620253pfj.1 for ; Thu, 01 Jun 2017 10:57:32 -0700 (PDT) In-Reply-To: <20170601140137.GB18840@bidouze.vm.6wind.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, 1 Jun 2017 16:01:37 +0200 Ga=C3=ABtan Rivet wrote: > What is necessary is a common piece of info (it can be MAC address, a > class Id, anything else) that allows a script to detect that the right > device has been plugged in. As long as the NFV server allows determinism > here, the user will be able to use its VF. There is a serial number property (GUID) on vmbus that is what Windows uses to associate VF and SF device. It maybe visible over sysfs. But it make senses to put that kind of system dependent matching rule in some other place (DPDK bus logic? or external daemon).