DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 2/2] mk: move PMD libraries to applications
Date: Fri, 10 Feb 2017 11:04:42 +0100	[thread overview]
Message-ID: <3212772.meQXQKO1QH@xps13> (raw)
In-Reply-To: <20170131150448.8294-2-ferruh.yigit@intel.com>

2017-01-31 15:04, Ferruh Yigit:
> Some PMDs provide device specific APIs. Bond and xenvirt are existing
> samples for this.
> 
> And since these are PMD libraries, there are two options on how to link
> them for shared library build:
> 
> 1- They can be linked to all applications by default, using common
> rte.app.mk file.
> 
> 2- They can be explicitly linked to applications that use device
> specific API.
> 
> Currently option one is in use, this patch switches to the option two.
> 
> Moves library linking to the Makefile of application Makefile that uses
> device specific API.
> 
> This prevent these PMD libraries to be a dependency to applications
> that don't use these device specific APIs.
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>

Series applied, thanks

      reply	other threads:[~2017-02-10 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 12:14 [dpdk-dev] [PATCH 1/2] app/testpmd: use LDLIBS in makefile Ferruh Yigit
2017-01-31 12:14 ` [dpdk-dev] [PATCH 2/2] mk: move PMD libraries to applications Ferruh Yigit
2017-01-31 14:16   ` Thomas Monjalon
2017-01-31 14:36     ` Ferruh Yigit
2017-01-31 15:04 ` [dpdk-dev] [PATCH v2 1/2] app/testpmd: use LDLIBS in makefile Ferruh Yigit
2017-01-31 15:04   ` [dpdk-dev] [PATCH v2 2/2] mk: move PMD libraries to applications Ferruh Yigit
2017-02-10 10:04     ` Thomas Monjalon [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=3212772.meQXQKO1QH@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).