From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 325A7271 for ; Thu, 29 Jun 2017 09:50:44 +0200 (CEST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2017 00:50:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,279,1496127600"; d="scan'208";a="118793661" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga005.jf.intel.com with ESMTP; 29 Jun 2017 00:50:43 -0700 Received: from FMSMSX110.amr.corp.intel.com (10.18.116.10) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 29 Jun 2017 00:50:43 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx110.amr.corp.intel.com (10.18.116.10) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 29 Jun 2017 00:47:34 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.146]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.122]) with mapi id 14.03.0319.002; Thu, 29 Jun 2017 15:47:33 +0800 From: "Guo, Jia" To: "Wu, Jingjing" , Stephen Hemminger CC: "Zhang, Helin" , "dev@dpdk.org" , "Chang, Cunyin" , "Liang, Cunming" Thread-Topic: [dpdk-dev] [PATCH v2 2/2] net/i40e: add hot plug monitor in i40e Thread-Index: AQHS7/8+mde7/q7Nj0+fGmEJuTbU4aI6qy2AgAAUfoCAALJqkA== Date: Thu, 29 Jun 2017 07:47:32 +0000 Message-ID: <01BA8470C017D6468C8290E4B9C5E1E83B23E394@shsmsx102.ccr.corp.intel.com> References: <1495986280-26207-1-git-send-email-jia.guo@intel.com> <1498648044-57541-1-git-send-email-jia.guo@intel.com> <1498648044-57541-2-git-send-email-jia.guo@intel.com> <20170628203441.22e9dbb8@xeon-e3> <9BB6961774997848B5B42BEC655768F810DB5BBA@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <9BB6961774997848B5B42BEC655768F810DB5BBA@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2 2/2] net/i40e: add hot plug monitor in i40e X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2017 07:50:45 -0000 Agree with jingjing. That patch is definitely not for generic fashion of hot plug, the uevent j= ust give the adding approach to monitor the remove event even if the drive= r not add it as interrupt , we know mlx driver have already implement the e= vent of remove interrupt into their infinite framework driver, but other dr= iver maybe not yet. So uevent is not unique for i40e or other intel nic, the aim just let more = diversity drivers which use pci-uio framework to use the common hot plug f= eature in DPDK. Best regards, Jeff Guo -----Original Message----- From: Wu, Jingjing=20 Sent: Thursday, June 29, 2017 12:48 PM To: Stephen Hemminger ; Guo, Jia Cc: Zhang, Helin ; dev@dpdk.org; Chang, Cunyin ; Liang, Cunming Subject: RE: [dpdk-dev] [PATCH v2 2/2] net/i40e: add hot plug monitor in i4= 0e > -----Original Message----- > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > Sent: Thursday, June 29, 2017 11:35 AM > To: Guo, Jia > Cc: Zhang, Helin ; Wu, Jingjing=20 > ; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v2 2/2] net/i40e: add hot plug monitor=20 > in i40e >=20 > On Wed, 28 Jun 2017 19:07:24 +0800 > Jeff Guo wrote: >=20 > > From: "Guo, Jia" > > > > This patch enable the hot plug feature in i40e, by monitoring the=20 > > hot plug uevent of the device. When remove event got, call the app=20 > > callback function to handle the detach process. > > > > Signed-off-by: Guo, Jia > > --- >=20 > Hot plug is good and needed. >=20 > But it needs to be done in a generic fashion in the bus layer. > There is nothing about uevents that are unique to i40e or even Intel devi= ces. > Plus the way hotplug is handled is OS specific, so this isn't going to=20 > work well on BSD. >=20 This patch is not a way to full support hut plug. And we know it is handled= in OS specific. This patch just provides a way to tell DPDK user the remove happened on thi= s device (DPDK dev). And Mlx driver already supports that with patch http://dpdk.org/dev/patchwo= rk/patch/23695/ What GuoJia did is just making the EVENT can be process by application thro= ugh interrupt callback Mechanisms. > Sorry if I sound like a broken record but there has been a repeated=20 > pattern of Intel developers putting their head down (or in the sand)=20 > and creating functionality inside device driver. Sorry, I cannot agree. Thanks Jingjing