From: Kumaraparameshwaran Rathnavel <krath at cloudsimple.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] DPDK
Date: Wed, 02 Nov 2016 21:57:59 +0530 [thread overview]
Message-ID: <76DB3DFD-CD78-496F-A95A-B39DFB586C03@cloudsimple.com> (raw)
In-Reply-To: a14fddec-b412-dffd-4751-3d686d2ddd65@intel.com
[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]
Thanks for the Reply Daniel.
Thanking You,
Param
Sent from my iPhone
> On 02-Nov-2016, at 9:48 PM, Daniel Verkamp <daniel.verkamp(a)intel.com> wrote:
>
>> On 11/02/2016 04:47 AM, Kumaraparameshwaran Rathnavel wrote:
>> Hi All,
>>
>> I am writing an application similar to nvmf target in SPDK. I should not use the Makefile format given for nvmf target. I am having my own cmake file and I have included libraries and header files from DPDK and SPDK. My application core dumps at rte_mempool_create. When I use the same code and the format of the Makefile in nvmf target it doesn't. I can see that I am missing some flags r something. Can any one help me? Is there an implementation of Makefiles of nvmf target in SPDK with cmake
>>
>> Thanking you,
>> Param
>
> Hi Param,
>
> We would have to see a backtrace to be sure, but it is likely that your build system is not linking the DPDK libraries correctly. If you are using DPDK 16.07 or newer built as static libraries, you need to link the rte_* libraries with the -Wl,--whole-archive linker option to ensure none of the object files that contain only constructors get eliminated. Some of the mempool functionality was made pluggable and moved to initialization in constructors in DPDK 16.07, and if you fail to link the libraries this way, you will end up with NULL function pointers. Alternatively, you can just use a shared library build of DPDK.
>
> See commit 20c11032aecc9678b415dc1861607d5f46ec34ef in SPDK for how this issue was fixed in our Makefile build system.
>
> Thanks,
> -- Daniel
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2016-11-02 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 16:27 Kumaraparameshwaran Rathnavel [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-02 17:28 [SPDK] DPDK Alex Bowden
2016-11-02 16:44 Kumaraparameshwaran Rathnavel
2016-11-02 16:18 Daniel Verkamp
2016-11-02 11:47 Kumaraparameshwaran Rathnavel
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=76DB3DFD-CD78-496F-A95A-B39DFB586C03@cloudsimple.com \
--to=spdk@lists.01.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