From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 8E1A1200 for ; Fri, 8 Dec 2017 12:06:38 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1109420C8C; Fri, 8 Dec 2017 06:06:38 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 08 Dec 2017 06:06:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=VWOqd8fkiGVxffhrbXqnB6VeHF mv+GFNlvtIf3qt1aQ=; b=H5Ijzgpp9SLc3iOhqp+Us6IPYTvJS43dXe2YM9kkcK 5thi0HxJsABSHbjWjB34l06oGDYtmVW3P4zhn/K8vQv78VtGIkN81j1B5yCUprQz 47vy61fNnBGjQprm6zLT+DAH4wk7BIa1WyVQcr5s9kcG4ywWqK9COuNoQWOSv+DK A= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=VWOqd8 fkiGVxffhrbXqnB6VeHFmv+GFNlvtIf3qt1aQ=; b=h4X19nBAjiGiMRvXovBkWs foZinkFYhzQceAK5UzJYBytGKE5xtq46bMEU8rWhjh1lgTkOC+RJlORQk8iNmcOL RGD5pbGu4Wv05r/AIsvkJoHJLyVLZQPDln1jnUcHiknfGOi1ssKmyFfcROkFg2m3 LbRLMFrsBsTyVGzkFiuHAZBmHlAqixR7AR1z97kcDc3+LkLjXyThS+SVsZAJN9CV 8II3AVwr+qQnTowTRnuKqBkt9RNzdDJ6d9Ruv4ndut01uVo6h/6RWyeAK2f98s9D f7iAO8/bXc11njO3S/tgMszERjgE1NExJxC1PfG82HD/tTnab7SzkYuxPCCeFGFg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id BA3837E56E; Fri, 8 Dec 2017 06:06:37 -0500 (EST) From: Thomas Monjalon To: Neil Horman Cc: Matan Azrad , "Ananyev, Konstantin" , =?ISO-8859-1?Q?Ga=EBtan?= Rivet , "Wu, Jingjing" , dev@dpdk.org Date: Fri, 08 Dec 2017 12:06:36 +0100 Message-ID: <4385808.uF5lz4cc4W@xps> In-Reply-To: <20171205192640.GC10327@hmswarspite.think-freely.org> References: <20171130123611.GA20914@hmswarspite.think-freely.org> <20171205192640.GC10327@hmswarspite.think-freely.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 2/5] ethdev: add port ownership 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: Fri, 08 Dec 2017 11:06:38 -0000 05/12/2017 20:26, Neil Horman: > I get that much of dpdk relies on the fact that the application either handles > all the locking, or architects itself so that a single thread of execution (or > at least only one thread at a time), is responsible for packet processing and > port configuration. Yes, for now, configuration is synchronized at application level. It is a constraint for applications. It may be an issue for multi-process applications, or for libraries aiming some device management. The first obvious bug to fix is race in device allocation. It will become more real with hotplug support.