DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: mukawa@igel.co.jp
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: Tue, 30 Sep 2014 07:23:53 -0400	[thread overview]
Message-ID: <20140930112353.GA2193@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1412070970-5625-3-git-send-email-mukawa@igel.co.jp>

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.

Neil

>  ifeq ($(CONFIG_RTE_BUILD_SHARED_LIB),n)
>  # plugins (link only if static libraries)
>  
> -- 
> 1.9.1
> 
> 

  reply	other threads:[~2014-09-30 11:17 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 [this message]
2014-10-01  1:39     ` Tetsuya Mukawa

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=20140930112353.GA2193@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=dev@dpdk.org \
    --cc=masutani.hitoshi@lab.ntt.co.jp \
    --cc=mukawa@igel.co.jp \
    --cc=nakajima.yoshihiro@lab.ntt.co.jp \
    /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).