From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 14FB8A0487 for ; Tue, 30 Jul 2019 10:16:31 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 548BB1BFD6; Tue, 30 Jul 2019 10:16:30 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id CD97C1BDF1; Tue, 30 Jul 2019 10:16:28 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 686042094D; Tue, 30 Jul 2019 04:16:28 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 30 Jul 2019 04:16:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=0HU53DdDjqiuMaQDKw3+lEPid4kY4UlZFEpGqg+4jZs=; b=r9JCuyAjc9MP Ok/SAYt3ohWgTtnxfr8H1N1WDH1/EDoNZ9JXcifUxNLPYAoIceT4zgYXGh3OSga6 x4Su/ucglU1SSrFn+4/rz4NFjQ48aikqynrHEoT2qzW8QwqH7SN/lHQ5g7/L9+Z9 2ismWTqejXpj4AHh/dGU+IUkYVFXTwk= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=0HU53DdDjqiuMaQDKw3+lEPid4kY4UlZFEpGqg+4j Zs=; b=CbQdQKOciUX+yhnjPiCs8+3l1/TLSLH2n2W/tJLQpqYXop7HJfWz7BRkb 6R8xZZa0ROWM6gy+4wriBAYHj5Ixtw23O5NpTWDg7d5GIt5892vbN0Te/JgsZoYu ee4Gm34RPMmVOxY+9kHPZMlpEW6fXFOlL7XJbtMJrmOqWRY08wADmw4HAMBO5raV 3UV2TrUcu9MBwCXjm5CNfUZZU02wP0uV8yiYtZa+XSwjLnXNnJ4MOaH0fBSUdatp 0ci5xpyEN8Lzr09zoLkstxy2kywpY/ZpkxoJYA3CngsmjUyYu6qAPP5RcmiNtJ13 uY648bZ0CeATGjHPF2smChxOoP1PA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrleefgddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 99072380085; Tue, 30 Jul 2019 04:16:26 -0400 (EDT) From: Thomas Monjalon To: "Burakov, Anatoly" , yasufum.o@gmail.com, Yasufumi Ogawa Cc: stable@dpdk.org, david.marchand@redhat.com, dev@dpdk.org Date: Tue, 30 Jul 2019 10:16:25 +0200 Message-ID: <2145389.2zrQCyyVWU@xps> In-Reply-To: <680b4b57-48c3-8a5c-09b3-7d28cea40d45@intel.com> References: <20190711103148.9187-1-yasufum.o@gmail.com> <20190724082031.45546-2-yasufum.o@gmail.com> <680b4b57-48c3-8a5c-09b3-7d28cea40d45@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v4 1/1] fbarray: get fbarrays from containerized secondary 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 24/07/2019 11:59, Burakov, Anatoly: > On 24-Jul-19 9:20 AM, yasufum.o@gmail.com wrote: > > From: Yasufumi Ogawa > > > > In secondary_msl_create_walk(), it creates a file for fbarrays with its > > PID for reserving unique name among secondary processes. However, it > > does not work if secondary is run as app container because each of > > containerized secondary has PID 1. To reserve unique name, use hostname > > instead of PID because hostname is assigned as a short form of 64 > > digits full container ID in docker. > > > > Cc: stable@dpdk.org > > > > Signed-off-by: Yasufumi Ogawa > > Acked-by: Anatoly Burakov This may change the behaviour, so this fix is deferred to 19.11 release cycle. OK?