From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id D84FF6A8B for ; Wed, 10 Dec 2014 15:48:27 +0100 (CET) Received: from nat-pool-rdu-t.redhat.com ([66.187.233.202] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1XyiYe-00027b-4f; Wed, 10 Dec 2014 09:48:11 -0500 Date: Wed, 10 Dec 2014 09:47:45 -0500 From: Neil Horman To: "Wodkowski, PawelX" Message-ID: <20141210144745.GC17040@localhost.localdomain> References: <1404818184-29388-1-git-send-email-danielx.t.mrzyglod@intel.com> <20141208144545.GD3237@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Score: -2.9 (--) X-Spam-Status: No Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Added Spinlock to l3fwd-vf example to prevent race conditioning 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: Wed, 10 Dec 2014 14:48:28 -0000 On Wed, Dec 10, 2014 at 08:18:36AM +0000, Wodkowski, PawelX wrote: > > Though, that said, doesn't it seem to anyone else like serialization of enqueue > > to a port should be the responsibility of the library, not the application? > > > > Neil > > From my knowledge it is an application responsibility to serialize access to > queue on particular port. > I understand thats the way it currently is, I'm advocating for the fact that it should not be. Neil > Pawel >