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 7C74BA00BE; Mon, 27 Apr 2020 13:40:14 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3E0181D16A; Mon, 27 Apr 2020 13:40:13 +0200 (CEST) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by dpdk.org (Postfix) with ESMTP id 935AD1D159 for ; Mon, 27 Apr 2020 13:40:11 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailnew.nyi.internal (Postfix) with ESMTP id E5832580086; Mon, 27 Apr 2020 07:40:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Mon, 27 Apr 2020 07:40:10 -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=fm1; bh= 4sxyyzIIUkyAkLaoWpXAU5co9jdUBZBqwtGyXR94Z+Q=; b=TkAa1CoT73LUYrIe t8PaZhNpxTBb8WZ2bVJDtoF5qUqwSzqoBzF+2Tm45hySeapXpnUuqxY9pVWwYOgQ k4yyOdGG75XPS9z7Q8mzAaj/90L10LV+2z2B5/kzVARNLxcOeEee468Lq6Zq3k0v xS2Eqt/C9bMC+Do1Dm5zTOZP/AVlD+ZwcBQej5i2QklgtxLue8O28Xy5YsLNOP5D XYD0vCzQV2+Yns4Jqow1L21PtTBo0ptZRzZ6/JqRgDi5YGQbsQr6gkkm5sin7s48 1wZNDs3ibFqLquEZfJiQX0usQWJ8AvTjwcjwFs5eMPCA1NaH17eR9eKO9K97Hkj0 GJ6hvw== 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=fm2; bh=4sxyyzIIUkyAkLaoWpXAU5co9jdUBZBqwtGyXR94Z +Q=; b=TcGkPCml+0XRy06TP5ZnRWv7/2pnFResTeyL3P/QbzcePKSnWHhRqr0lN D5qqObx9VKUx+FqidvtGkNHIN3K1VdH8jeZ7azKrTAgrzSNG6dyvHa5gAVoka3mT 88BEoFgBzL0A5/UsYwLDjFTMmbScWrBdvn15Rob6rzdJoe9VfJjytYdIeUqbqcc1 sZc5aILfzfmDpFFlAdBdDDIgzui7HaDbQhpMg9tgJnLzJPCTNKAC7Un8Eo2O6FAC IrqHBI8RdhXH6bPlp4Jz8JpsHS5ZAj+6yewMGmzQkmr2LLIIVyxK0CRGzV2WSHEN icQffp2D3SbWqsJPsz3kDprPprIow== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrheelgdegudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth 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 5A3F03065E60; Mon, 27 Apr 2020 07:40:08 -0400 (EDT) From: Thomas Monjalon To: Tonghao Zhang Cc: Olivier Matz , Andrew Rybchenko , Gage Eads , "Artem V. Andreev" , Jerin Jacob , Nithin Dabilpuram , Vamsi Attunuru , Hemant Agrawal , David Marchand , "Burakov, Anatoly" , Bruce Richardson , dpdk-dev Date: Mon, 27 Apr 2020 13:40:06 +0200 Message-ID: <9453419.OU7Dqq5WaI@thomas> In-Reply-To: References: <1583114253-15345-1-git-send-email-xiangxia.m.yue@gmail.com> <3331280.0S5aU1g85B@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH dpdk-dev v3 2/2] mempool: use shared memzone for rte_mempool_ops 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" 27/04/2020 10:03, Tonghao Zhang: > On Fri, Apr 17, 2020 at 6:27 AM Thomas Monjalon wrote: > > > > 13/04/2020 16:21, xiangxia.m.yue@gmail.com: > > > The order of mempool initiation affects mempool index in the > > > rte_mempool_ops_table. For example, when building APPs with: > > > > > > $ gcc -lrte_mempool_bucket -lrte_mempool_ring ... > > > > > > The "bucket" mempool will be registered firstly, and its index > > > in table is 0 while the index of "ring" mempool is 1. DPDK > > > uses the mk/rte.app.mk to build APPs, and others, for example, > > > Open vSwitch, use the libdpdk.a or libdpdk.so to build it. > > > The mempool lib linked in dpdk and Open vSwitch is different. > > > > We are supposed to use pkg-config to link DPDK. > > Does the problem appear between a DPDK compiled with meson > > and an application linked with pkg-config information? > > > > If the problem really needs to be solved, > > the EAL patch (first of this series) needs to be discussed > > and reviewed carefully. I don't imagine it being done in 20.05. > > will I stop update the patches or when the patch is ready and then > decide applied or not? As I said, it requires more discussion. Please start by answering my question above.