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 31902A04E7; Sun, 15 Nov 2020 15:23:45 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1EF56C8F4; Sun, 15 Nov 2020 15:23:26 +0100 (CET) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) by dpdk.org (Postfix) with ESMTP id 34C10C8F2; Sun, 15 Nov 2020 15:23:23 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id EC2F416CD; Sun, 15 Nov 2020 09:23:20 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sun, 15 Nov 2020 09:23:21 -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=fm2; bh= gm561tDT9ASEoELKwVcUY5UfLrH1s2YAx4KK6Op4tE4=; b=onyBhIHWV4GnPHys OA+frAtAZN5zXVLVY5y9GbVUksVqrwlcDDFQpnXLTBmN6XJ53rjU1B1eO26AXm8M XI3gvyXjZl1Zw+k4c87398XxH8f/xO+PZE6Ae/AYqwwc5dbK6+fos2xpB4mrlIJd NiU09o4dODwTgYbuHp19HJzRMsfdDoN3HuuvCqjgyGvcS5eFsz5ACNUb5i9ovRUW 49EhLpIkyjdjN8DSWCnmIgmc9gYq9Ify1bAamQCjYuwnuOpcTCpCurocG609z5tH 6XhGSKAoyAOZg1RHpXyiQapMuazQPSygxngSq41L9TCvLltG6YvZuS53U6x77Xf5 ojlo3Q== 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=gm561tDT9ASEoELKwVcUY5UfLrH1s2YAx4KK6Op4t E4=; b=BeU/ybQd+qugE0NDyh5pdP9QDMbcYaw7gP7j5X01sDPBHByoqV+z9EGk5 NZ1bhjnNF6nqoCXvWy0EjCokPyEHsgufc4Jlow8Lg65QAfBrsgPHNKkuGyAhQV8J WuDypih2c3+Ft945nVdrq2aPeNaN37URRzmP4jBc2x+S0IRT3cAWp5NlMkJ8rM7L zFXo+Q970IW1glpI21M5FIRoPVVX2mwsPAdyOvEjzOhwtNLxic6quKx1w5MxiyhE 5lbKlb2vRh9mt6cVVA6DGAyKtBe/MSyhnZobvD9HvAeytwMCocdn2fRVfHssxQyW b1qMG9lgXPOd/5e34gHyNqF6iT/kQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedruddvledgieeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght 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 5239E3064AAA; Sun, 15 Nov 2020 09:23:19 -0500 (EST) From: Thomas Monjalon To: anatoly.burakov@intel.com, Yunjian Wang Cc: stable@dpdk.org, dev@dpdk.org, david.marchand@redhat.com, jerry.lilijun@huawei.com, xudingke@huawei.com, stable@dpdk.org Date: Sun, 15 Nov 2020 15:23:18 +0100 Message-ID: <6957254.HVmevjuWZl@thomas> In-Reply-To: <1768774.JEQ3pMzOXi@thomas> References: <1595515713-24640-1-git-send-email-wangyunjian@huawei.com> <1602840525-8848-1-git-send-email-wangyunjian@huawei.com> <1768774.JEQ3pMzOXi@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] eal: fix create user mem map repeatedly when it exists 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" 20/10/2020 16:09, Thomas Monjalon: > 16/10/2020 11:28, wangyunjian: > > From: Yunjian Wang > > > > Currently, a issue that a container has many devices and the > > application will map the same memory many times. The kernel > > driver returns EEXIST as long as there are overlapping memory > > areas. As a result, we repeatedly create new user mem map entry > > for the same memory segment and this will lead to no more space > > for other user mem maps. > > > > To resolve the issue, add support to remove the same entry in > > the function compact_user_maps(). > > Sorry I don't understand the explanations above. > Anatoly, please could you help in rewording? Ping for rewording please.