On Mon, Apr 27, 2020 at 7:40 PM Thomas Monjalon <tho...@monjalon.net> wrote: > > 27/04/2020 10:03, Tonghao Zhang: > > On Fri, Apr 17, 2020 at 6:27 AM Thomas Monjalon <tho...@monjalon.net> wrote: > > > > > > 13/04/2020 16:21, xiangxia.m....@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
