From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Fix linking errors when CONFIG_RTE_BUILD_SHARED_LIB is enabled
Date: Thu, 02 Oct 2014 12:44:17 +0900 [thread overview]
Message-ID: <542CCA11.3050609@igel.co.jp> (raw)
In-Reply-To: <20141002024626.GA24668@mhcomputing.net>
(2014/10/02 11:46), Matthew Hall wrote:
> On Thu, Oct 02, 2014 at 10:43:52AM +0900, Tetsuya Mukawa wrote:
> It's worth pointing out that you're likely better off using
> COMBINE_LIBS to make one big static lib rather than using a shared lib
> or you're facing a performance loss from the dynamic linking overhead.
> Matthew.
Thanks. I will go over it
Regards,
Tetsuya
prev parent reply other threads:[~2014-10-02 3:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 4:27 mukawa
2014-10-01 10:50 ` Neil Horman
2014-10-01 11:56 ` Thomas Monjalon
2014-10-02 2:48 ` Tetsuya Mukawa
2014-10-02 8:12 ` Sergio Gonzalez Monroy
2014-10-02 8:28 ` Tetsuya Mukawa
2014-10-02 8:53 ` Sergio Gonzalez Monroy
2014-10-02 9:05 ` Tetsuya Mukawa
2014-10-03 11:11 ` Sergio Gonzalez Monroy
2014-10-02 1:43 ` Tetsuya Mukawa
2014-10-02 2:46 ` Matthew Hall
2014-10-02 3:44 ` 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=542CCA11.3050609@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).