From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org, nakajima.yoshihiro@lab.ntt.co.jp,
masutani.hitoshi@lab.ntt.co.jp
Subject: Re: [dpdk-dev] [PATCH 2/2] librte_pmd_null: Enable librte_pmd_null
Date: Wed, 01 Oct 2014 10:39:29 +0900 [thread overview]
Message-ID: <542B5B51.9010303@igel.co.jp> (raw)
In-Reply-To: <20140930112353.GA2193@hmsreliant.think-freely.org>
(2014/09/30 20:23), Neil Horman wrote:
> On Tue, Sep 30, 2014 at 06:56:10PM +0900, mukawa@igel.co.jp wrote:
>> From: Tetsuya Mukawa <mukawa@igel.co.jp>
>>
>> Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp>
>> ---
>> mk/rte.app.mk | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/mk/rte.app.mk b/mk/rte.app.mk
>> index 34dff2a..f059290 100644
>> --- a/mk/rte.app.mk
>> +++ b/mk/rte.app.mk
>> @@ -179,6 +179,10 @@ LDLIBS += -lrte_pmd_xenvirt
>> LDLIBS += -lxenstore
>> endif
>>
>> +ifeq ($(CONFIG_RTE_LIBRTE_PMD_NULL),y)
>> +LDLIBS += -lrte_pmd_null
>> +endif
>> +
> You don't need to add this, as the pmd can be loaded dynamically via the dlopen
> call executed via the -d option on the test app command line. The only pmds
> that need explicit linking are those that offer additional API calls to an
> appilcation.
Thanks, I will change above.
Regards,
Tetsuya
> Neil
>
>> ifeq ($(CONFIG_RTE_BUILD_SHARED_LIB),n)
>> # plugins (link only if static libraries)
>>
>> --
>> 1.9.1
>>
>>
prev parent reply other threads:[~2014-10-01 1:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 9:56 [dpdk-dev] [PATCH 0/2] PMD for performance measurement mukawa
2014-09-30 9:56 ` [dpdk-dev] [PATCH 1/2] librte_pmd_null: Add null PMD mukawa
2014-09-30 13:05 ` Thomas Monjalon
2014-10-01 1:41 ` Tetsuya Mukawa
2014-09-30 9:56 ` [dpdk-dev] [PATCH 2/2] librte_pmd_null: Enable librte_pmd_null mukawa
2014-09-30 11:23 ` Neil Horman
2014-10-01 1:39 ` Tetsuya Mukawa [this message]
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=542B5B51.9010303@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=dev@dpdk.org \
--cc=masutani.hitoshi@lab.ntt.co.jp \
--cc=nakajima.yoshihiro@lab.ntt.co.jp \
--cc=nhorman@tuxdriver.com \
/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).