DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 401] unit_tests: mempool_autotest failed with shared mode library
Date: Thu, 20 Feb 2020 05:48:55 +0000	[thread overview]
Message-ID: <bug-401-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=401

            Bug ID: 401
           Summary: unit_tests: mempool_autotest failed with shared mode
                    library
           Product: DPDK
           Version: 20.02
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: hailinx.xu@intel.com
  Target Milestone: ---

1.compile DPDK shared library based on DPDK 20.02-rc0
  # checkout to DPDK latest version (my ENV commit id is 
  10060dba6455461088d24e03d3cfeba639d53022)
  # set CONFIG_RTE_BUILD_SHARED_LIB=y in conf/common_base
  # compile DPDK
  # cp x86_64-native-linuxapp-gcc/lib/ /root/shared_lib_dpdk19.11/ -rf
  # export LD_LIBRARY_PATH=/root/shared_lib_dpdk19.11
2.compile DPDK APPs with shared mode library based on DPDK 19.11
  # git checkout v19.11
  # set CONFIG_RTE_BUILD_SHARED_LIB=y in conf/common_base
  # compile DPDK
3.Bind PF with vfio-pci
  # /root/dpdk/usertools/dpdk-devbind.py -b vfio-pci 86:00.0 86:00.1
4.start DPDK APP test with -d paramter
  # ./x86_64-native-linuxapp-gcc/app/test -n 1 -c 0xfffffffefffffffe -d
/root/shared_lib_dpdk19.11
5.input mempool_autotest and check output
  RTE>>mempool_autotest
  test_mempool ret = -22
  test failed at test_mempool():535
  Test Failed
  RTE>> 

#the output should contain 'Test OK', but it is as following:
test_mempool ret = -22
test failed at test_mempool():535
Test Failed
RTE>>

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-02-20  5:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-401-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).