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 63B1EA00BE; Mon, 27 Apr 2020 14:52:00 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 82B2C1D182; Mon, 27 Apr 2020 14:51:59 +0200 (CEST) Received: from mail-ej1-f67.google.com (mail-ej1-f67.google.com [209.85.218.67]) by dpdk.org (Postfix) with ESMTP id 65F2C1BED9 for ; Mon, 27 Apr 2020 14:51:57 +0200 (CEST) Received: by mail-ej1-f67.google.com with SMTP id a2so14012337ejx.5 for ; Mon, 27 Apr 2020 05:51:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=umB4IXGZAsDBxqGAyjEEKZrcK/pRlXgIPpofoZJAyis=; b=OJL0SJvehc7LEyIJ4vl1E5ABZDwxUmYLh1T5z+ICRBEOlQ/35j9seI7WR1FFsppmF5 o0Wy4hzrKWRAhSmpKsEGqn7ULXmplAAthyo5WxuhQYTtf62xTYoqASo3Tl6HrMU/FGWZ tdnJVCRJIclmWMrqBFfiSKJBd6TDSryz0KfwrjWd+HLMgTRVvvWM/6EaAR94CS/zhPau k+gN2EHQ0OEyLxZjkw/nKOwPSBgX1aCLpEeD9DzoMHXTZGHHycnjKPs1fFVO0HKbCsym gzm8jzLp/x3D/TY+oFElxPaIjLdgG4ywFV5dyqhRQhRVPee3uiCpB8QHJ8mC0SwOVcaz YYVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=umB4IXGZAsDBxqGAyjEEKZrcK/pRlXgIPpofoZJAyis=; b=bPC47GkxoBhd2S2uyXQDaH3LpypbgJIpoiDml3w/kWznPBeg7NoVWMtQrZFMWdCyAA nB5z9RX7qRMqSxIPDxyaLucFOB9ZImEFtlawV4KkqNVN/niLH7xGPGu+s9KhSoztKuno qO+PR7tgAN1yuTyS0fa7NnlOZ3Vc6ATEzFou0LdJ/lfbPiCbS7IoyAovhmzs2G1IlbPY YzL8JqxNDfSu7uv5aMX0WgsfbG8/85KknPL5ZDGXQlzclCZtBy0SSsO0ACt4OAC5auCY sh4dgEt45aIxAL1Ckwy1oWuVo8KMHyn44RMbUDwNcZevtRVkn36GEQIBwrXmCEbaz7VK /CLQ== X-Gm-Message-State: AGi0Pubh+i1iI5edHtpskQZ5DbQ8BkMmD2hfghIaL4VGF0n3CaQz2Ea3 RCoXosJxeP9RTvIC2VJAvSReSOeRX3r2dCdyYH32MVIhapg= X-Google-Smtp-Source: APiQypKMwZ+XejUlguwxQZc8TrTso+pHM1bd0Joh1K6VrQunn6lCi9CQZQIQOyDDmhsXBuGCRP8+q4vxAckNlpHmYLY= X-Received: by 2002:a17:906:6a02:: with SMTP id o2mr19121932ejr.223.1587991917149; Mon, 27 Apr 2020 05:51:57 -0700 (PDT) MIME-Version: 1.0 References: <1583114253-15345-1-git-send-email-xiangxia.m.yue@gmail.com> <3331280.0S5aU1g85B@thomas> <9453419.OU7Dqq5WaI@thomas> In-Reply-To: <9453419.OU7Dqq5WaI@thomas> From: Tonghao Zhang Date: Mon, 27 Apr 2020 20:51:20 +0800 Message-ID: To: Thomas Monjalon 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 Content-Type: text/plain; charset="UTF-8" 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" On Mon, Apr 27, 2020 at 7:40 PM Thomas Monjalon wrote: > > 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? Hi Thomas, The library mempool linked order can trigger that problem. but when the library is loaded dynamically, trigger that problem too. as Olivier Matz said: The fact that the ops index changes during mempool driver lifetime is indeed frightening, especially knowning that this is a dynamic registration that could happen at any moment in the life of the application. the message in https://mails.dpdk.org/archives/dev/2020-March/159354.html > > > 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. I got it, Thanks. > -- Best regards, Tonghao