From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shreyansh Jain Subject: Re: [PATCH 02/22] bus/vdev: enable one device scan Date: Fri, 8 Jun 2018 17:38:20 +0530 Message-ID: <81ec16de-38a4-9d9d-ba33-26378fd00d63@nxp.com> References: <20180607123849.14439-1-qi.z.zhang@intel.com> <20180607123849.14439-3-qi.z.zhang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: thomas@monjalon.net, anatoly.burakov@intel.com, konstantin.ananyev@intel.com, dev@dpdk.org, bruce.richardson@intel.com, ferruh.yigit@intel.com, benjamin.h.shelton@intel.com, narender.vangati@intel.com To: Qi Zhang Return-path: Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60040.outbound.protection.outlook.com [40.107.6.40]) by dpdk.org (Postfix) with ESMTP id D77ED5F72 for ; Fri, 8 Jun 2018 14:08:39 +0200 (CEST) In-Reply-To: <20180607123849.14439-3-qi.z.zhang@intel.com> Content-Language: en-US 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 6/7/2018 6:08 PM, Qi Zhang wrote: > Implemented the bus ops scan_one, besides this improve the scan > efficiency in hotplug case, it aslo avoid sync IPC invoke (which ^^^^ also > happens in vdev->scan on secondary process). The benifit is it ^^^^^^^ benefit > removes the potiential deadlock in the case when secondary process ^^^^^^^^^^ potential > receive a request from primary process to attach a new device, since > vdev->scan will be invoked on mp thread itself at this case. ^^^^^^^ in that Besides the above spells, is it possible to re-write the commit? You mention it "...improves the scan efficiency..." - how? Is that an implicit output of introducing the new scan_one for vdev? > > Signed-off-by: Qi Zhang > --- > drivers/bus/vdev/vdev.c | 30 ++++++++++++++++++++++++++++++ > 1 file changed, 30 insertions(+) > > diff --git a/drivers/bus/vdev/vdev.c b/drivers/bus/vdev/vdev.c > index 6139dd551..cdbd77df0 100644 > --- a/drivers/bus/vdev/vdev.c > +++ b/drivers/bus/vdev/vdev.c > @@ -467,6 +467,35 @@ vdev_scan(void) > return 0; > } > [...]