From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 2FB392C31 for ; Sun, 12 Jun 2016 07:27:58 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga103.fm.intel.com with ESMTP; 11 Jun 2016 22:27:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,460,1459839600"; d="scan'208";a="1000193133" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga002.fm.intel.com with ESMTP; 11 Jun 2016 22:27:58 -0700 Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sat, 11 Jun 2016 22:27:57 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx156.amr.corp.intel.com (10.18.116.74) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sat, 11 Jun 2016 22:27:57 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.147]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.230]) with mapi id 14.03.0248.002; Sun, 12 Jun 2016 13:27:55 +0800 From: "Lu, Wenzhuo" To: Stephen Hemminger CC: "dev@dpdk.org" , "Tao, Zhe" Thread-Topic: [dpdk-dev] [PATCH 2/8] lib/librte_ether: defind RX/TX lock mode Thread-Index: AQHRv7YPz+AiAd9UVkaKCUmVRYxRo5/eUdWAgADcisCAA1NigIAC1JOg Date: Sun, 12 Jun 2016 05:27:54 +0000 Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC090903484C1B@shsmsx102.ccr.corp.intel.com> References: <1465191653-28408-1-git-send-email-wenzhuo.lu@intel.com> <1465191653-28408-3-git-send-email-wenzhuo.lu@intel.com> <20160607191553.10993efe@xeon-e3> <6A0DE07E22DDAD4C9103DF62FEBC090903483A7F@shsmsx102.ccr.corp.intel.com> <20160610111227.4d9828f6@xeon-e3> In-Reply-To: <20160610111227.4d9828f6@xeon-e3> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: 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 2/8] lib/librte_ether: defind RX/TX lock mode X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2016 05:27:59 -0000 Hi Stephen, > -----Original Message----- > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > Sent: Saturday, June 11, 2016 2:12 AM > To: Lu, Wenzhuo > Cc: dev@dpdk.org; Tao, Zhe > Subject: Re: [dpdk-dev] [PATCH 2/8] lib/librte_ether: defind RX/TX lock m= ode >=20 > On Wed, 8 Jun 2016 07:34:43 +0000 > "Lu, Wenzhuo" wrote: >=20 > > > > > > The fact that it requires lots more locking inside each device > > > driver implies to me this is not correct way to architect this. > > It's a good question. This patch set doesn't follow the regular assumpt= ion of > DPDK. > > But it's a requirement we've got from some customers. The users want th= e > driver does as much as it can. The best is the link state change is trans= parent to > the users. > > The patch set tries to provide another choice if the users don't want t= o stop > their rx/tx to handle the reset event. >=20 > Then bring those uses to the development world (on users mailing list) an= d lets > start the discussion there. The requirements creeping in through the bac= kdoor > also worries me. Got it. Then how about we only provide a reset API and let the APP to stop/= start the rx/tx and call the API to reset the port? Thanks.