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 5311AA04DC; Tue, 20 Oct 2020 16:10:20 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3A1E4C325; Tue, 20 Oct 2020 16:09:12 +0200 (CEST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by dpdk.org (Postfix) with ESMTP id 62139BCD2; Tue, 20 Oct 2020 16:09:10 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id E5E2AD40; Tue, 20 Oct 2020 10:09:07 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 20 Oct 2020 10:09:08 -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=fm2; bh= In1X1OKSx0fTD5Ln9FyCz1pKhDT43aQ9MCi3uP+E0Us=; b=Rjw3F376MOSt+pqn 4rlskSWNheduwhLVN/F1HgA0wW9tS/DOnY58VpSpcaDz1tUPB1szvRfd1GN9YxM7 OghhJOzjEVlFlMB4J8XQ/KRyzo2AXUle5DWkHs77YODD0MeHpfPciQ2g/Fvt20qi f3wf1EWjIXbC1OY7h8TZzYgpSv0m5vl2zdUdcLUFfuOi7HaP90JKJ5AtGdU0M/YV IakI+6etOHrwWFIgzzj0WLetBNeGdnI9wdlZ6k8L8/qeCY59i51H1NEiJUqIWSd5 B3PA9SqPf94cIBAlGTjkLNYFGYEhui/rmFwJ0e0y1UxcnmiE9iYNb46wjCbd7U9a 96ALZA== 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=In1X1OKSx0fTD5Ln9FyCz1pKhDT43aQ9MCi3uP+E0 Us=; b=ATmfvp+N1yfz8WJAV6mYz6+hBrkI2DQkJiS8FK9Ot8D/4GFv3xmrGrgSl +gAgb9YtI9/B226Tx+v3+2hFOtWV7AmkEyLEOKYgF63nw8r4AmiPIXs8G6JG3zgd 606DqT1mj2Rcxcc5+UY77D6xEPEkFS/M83oWiB7fRAa8ss/+W1OkLvBUcp9NGrUd 5NIotOVb5GjckRr8vF2av5+74EExSTzeYvplfWUexl200+jKWxMRcVp1s/zO6SNv +4cffxMt8xaIn31ehXOYMxCO2J33JcazdXZZuwIWd4cT+BlfyvQfBRNkBwFTOXEZ 3jvGvjZnk9v72R8IdYGKa4ziSgsUQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrjeefgdejudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth 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 13D373064682; Tue, 20 Oct 2020 10:09:05 -0400 (EDT) From: Thomas Monjalon To: anatoly.burakov@intel.com, Yunjian Wang Cc: dev@dpdk.org, david.marchand@redhat.com, jerry.lilijun@huawei.com, xudingke@huawei.com, stable@dpdk.org Date: Tue, 20 Oct 2020 16:09:04 +0200 Message-ID: <1768774.JEQ3pMzOXi@thomas> In-Reply-To: <1602840525-8848-1-git-send-email-wangyunjian@huawei.com> References: <1595515713-24640-1-git-send-email-wangyunjian@huawei.com> <1602840525-8848-1-git-send-email-wangyunjian@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [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" 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?