From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 6DE963230 for ; Mon, 13 Jun 2016 11:18:05 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP; 13 Jun 2016 02:18:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,466,1459839600"; d="scan'208";a="718170607" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.58]) by FMSMGA003.fm.intel.com with SMTP; 13 Jun 2016 02:18:02 -0700 Received: by (sSMTP sendmail emulation); Mon, 13 Jun 2016 10:18:01 +0025 Date: Mon, 13 Jun 2016 10:18:01 +0100 From: Bruce Richardson To: Bernard Iremonger Cc: dev@dpdk.org, declan.doherty@intel.com, konstantin.ananyev@intel.com Message-ID: <20160613091800.GA17996@bricha3-MOBL3> References: <1464280727-25752-2-git-send-email-bernard.iremonger@intel.com> <1465751489-10111-1-git-send-email-bernard.iremonger@intel.com> <1465751489-10111-4-git-send-email-bernard.iremonger@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1465751489-10111-4-git-send-email-bernard.iremonger@intel.com> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v3 3/4] bonding: take queue spinlock in rx/tx burst functions 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: Mon, 13 Jun 2016 09:18:05 -0000 On Sun, Jun 12, 2016 at 06:11:28PM +0100, Bernard Iremonger wrote: > Use rte_spinlock_trylock() in the rx/tx burst functions to > take the queue spinlock. > > Signed-off-by: Bernard Iremonger > Acked-by: Konstantin Ananyev > --- Why does this particular PMD need spinlocks when doing RX and TX, while other device types do not? How is adding/removing devices from a bonded device different to other control operations that can be done on physical PMDs? Is this not similar to say bringing down or hotplugging out a physical port just before an RX or TX operation takes place? For all other PMDs we rely on the app to synchronise control and data plane operation - why not here? /Bruce