From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id B4B7B1D8E
 for <dev@dpdk.org>; Tue,  5 Dec 2017 09:41:11 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 416E620FCB;
 Tue,  5 Dec 2017 03:41:09 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
 by compute1.internal (MEProxy); Tue, 05 Dec 2017 03:41:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc; s=mesmtp; bh=EGHAfUNve835u8n9yLKsjZk/N9
 a0aRxPOHL0JgwI/Jk=; b=GB0viUNwTPRV3KpfIZjZm/lfAU8+szt4ypgT2fRvV5
 jWn7ja2rvBbYKHVAvbaJfpfhgtYHAVCyjYNBI/lpTwRKxzg2Fo6IeVHN7PbtbWhe
 3LyBoyBBZZQ2lfOqbDC8vRMdsvvNGNsAZGQmpQjUOFVB4eV3zfpZQ7FhaVqXHNPc
 4=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=EGHAfU
 Nve835u8n9yLKsjZk/N9a0aRxPOHL0JgwI/Jk=; b=BkDkp9xbCRbWkLCEqEcZQV
 3YbJ83NhhOn9elSlss3SZLfTQSeSdYEPRp/iM24gZZvlTniIVYIqCDe48bfleubd
 4x+GFs/FhBjykKolsL73NL+HvQOm23eMTKYvx/g8dB4hkiLfs1GDAWI+d6EZVP2u
 PKBVsaWC9xDU8FubWARicveqRH6kmQRrN4SPAMDFeoz1uM9TFf6Iw1aYo0+6Ol0M
 A9gxCfIfkyT6y1IRzy1syyWTok4clmp8RXHRHxxT130SuhihJ3KPz/kq0iI1lMpI
 IU8fgpmrPxL+iXJg9rmsgofEiwT0dTm7xH/JC4kJBE89ljNZX+Z6ZLvb9of09Anw
 ==
X-ME-Sender: <xms:pVsmWkiCIB-LtZuP9dIfIXIOiGbvSCuF1aL6QnLwhYsEwTSXV1VHHA>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id E0A8A7E8BF;
 Tue,  5 Dec 2017 03:41:08 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>
Cc: dev@dpdk.org
Date: Tue, 05 Dec 2017 09:41:07 +0100
Message-ID: <5374836.XgGFu4empV@xps>
In-Reply-To: <fd26c5ea-bbff-8036-cd54-b9f7fb1f1926@intel.com>
References: <20171201003642.19827-1-thomas@monjalon.net>
 <2579199.neyJOE5Nyd@xps> <fd26c5ea-bbff-8036-cd54-b9f7fb1f1926@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [dpdk-dev] [PATCH] bus/vdev: add custom scan hook
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://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: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Dec 2017 08:41:12 -0000

05/12/2017 09:27, Tan, Jianfeng:
> 
> On 12/4/2017 5:31 PM, Thomas Monjalon wrote:
> >
> > The hook is in bus->scan().
> > I think we should launch a bus scan when there is a new device event.
> 
> That's what I'm trying to say. We finally need to execute a handler as 
> of a device event to finish the job.

Please be more specific, I am not sure to understand.

> Then why not just keep the vdev plug in that handler, by calling 
> rte_dev_hotplug_add()?

Which handler?