From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 5F0191BD1B; Thu, 20 Dec 2018 15:29:19 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id F21ED21EAD; Thu, 20 Dec 2018 09:29:18 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 20 Dec 2018 09:29:19 -0500 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=SkaplnWFYQbkDKINpjHWb07dhEUEAHIwEO4lJixpjH0=; b=pNpRdcSmw4cK LCb6oN9UmPrTEnbF5gUi6TSm/AQbvzK903rrTL3gezqq2bukbAYglCWkAEoB/u/Q fsGX7SBxevobYkemd6rY0qzj/ZJzLqMdeCOHjauav/cjVsUImM/bESGMG8s2S8oo O0136FjQcRzPNcfOff6MlUbcWf3g6yA= 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=fm1; bh=SkaplnWFYQbkDKINpjHWb07dhEUEAHIwEO4lJixpj H0=; b=gn+y8eaSL3jchdDc5edFwpZ6nF3ujPNDr7FBwVa24oKka1wTzMa4oZX61 Qhm8JH4/iz8C2+hvg5uiQMDxbtC0boMiIFmReLxiK+rJTsNAiGd4i9ogDsogdBJa pfbeIxFH4H7zBp4ldjDVCnlldCXpcw0QOwV8mZqYwgQuND7a0IKaFbM80jZFt9/4 Krw9YBecYaUxcT5/DTm0ipPSYewf29LFsyrTfExJg+UoHNmeEvAUDcjVqGsNh9bC 6Q/Ijg0jZEQB9kZRFw5JLDGDK//Yt4yz7GJ8EF+fbWPd/2NtfgBhB4JQP59+k4Ew vHgU83ll1/E8ObkMyXmv2rSYOtuHg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudejfedgieejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvffufffkjg hfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcu oehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtd efrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 D9A2F10085; Thu, 20 Dec 2018 09:29:17 -0500 (EST) From: Thomas Monjalon To: Anatoly Burakov Cc: stable@dpdk.org, dev@dpdk.org, keith.wiles@intel.com Date: Thu, 20 Dec 2018 15:29:16 +0100 Message-ID: <2039593.hqcdMvUHT9@xps> In-Reply-To: <4934d38eb70f2951f9212bd4d7e35ceb9d982321.1544546857.git.anatoly.burakov@intel.com> References: <4934d38eb70f2951f9212bd4d7e35ceb9d982321.1544546857.git.anatoly.burakov@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] malloc: fix duplicate mem event notification 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: Thu, 20 Dec 2018 14:29:19 -0000 11/12/2018 17:48, Anatoly Burakov: > We already trigger a mem event notification inside the walk function, > no need to do it twice. > > Fixes: f32c7c9de961 ("malloc: enable event callbacks for external memory") > Cc: stable@dpdk.org > > Signed-off-by: Anatoly Burakov Applied, thanks