DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Performance - linking against DPDK shared vs static libraries
Date: Wed, 23 Jul 2014 14:56:14 -0700	[thread overview]
Message-ID: <20140723215614.GA19555@mhcomputing.net> (raw)
In-Reply-To: <DC5AD7FA266D86499789B1BCAEC715F846BA3CFA@IRSMSX105.ger.corp.intel.com>

On Wed, Jul 23, 2014 at 09:43:49PM +0000, Kavanagh, Mark B wrote:
> I take it ... that the performance drop when using shared libraries is 
> expected behavior?

s/expected behavior/and unavoidable consequence/g

;)

Matthew Hall.

  reply	other threads:[~2014-07-23 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 15:58 Kavanagh, Mark B
2014-07-23 16:37 ` Antti Kantee
2014-07-23 21:43   ` Kavanagh, Mark B
2014-07-23 21:56     ` Matthew Hall [this message]
2014-07-24 14:02       ` Kavanagh, Mark B
2014-07-23 18:08 ` Stephen Hemminger

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=20140723215614.GA19555@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=mark.b.kavanagh@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).