From: jigsaw <jigsaw@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Is it possible to have dpdk running with no dependency on a nic ?
Date: Mon, 17 Feb 2014 14:49:47 +0200 [thread overview]
Message-ID: <CAHVfvh4-KNT8EaGZ_HZaWwYEZ45QD3DO1znYZEXMO0Dy_Aiceg@mail.gmail.com> (raw)
In-Reply-To: <20140216110241.0e789750@nehalam.linuxnetplumber.net>
Hi Stephen,
Have you tried link time optimization on DPDK application? Does it
decrease the I-cache miss rate evidently?
thx &
rgds,
-Qinglai
On Sun, Feb 16, 2014 at 9:02 PM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> On Fri, 14 Feb 2014 15:11:29 -0500
> Ymo Lists <ymolists@gmail.com> wrote:
>
>> "Enqueuing and dequeuing items from an rte_ring using the rings-based PMD
>> may be slower than using the native rings API. This is because Intel® DPDK
>> Ethernet drivers make use of function pointers to call the appropriate
>> enqueue or dequeue functions, while the rte_ring specific functions are
>> direct function calls in the code and are often inlined by the compiler."
>>
>> Is that statement correct ? I would imagine that inlined code would be be
>> faster than using function pointers ?
>
> Actually, the Intel DPDK has a bad case of inlineitis. The code for ring's
> and other parts use inline on largish functions which bloats the code without
> any perceivable gain in performance. The larger code causes more cache misses
> which actually hurt performance. Also using GCC link time optimization helps
> to reduce any need for inlining larger code bits.
next prev parent reply other threads:[~2014-02-17 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 18:21 Ymo Lists
2014-02-13 20:19 ` Ymo Lists
2014-02-14 8:42 ` Vivek Soni
2014-02-14 17:20 ` Ymo Lists
2014-02-14 18:20 ` Jayakumar, Muthurajan
2014-02-14 20:11 ` Ymo Lists
2014-02-16 19:02 ` Stephen Hemminger
2014-02-17 12:49 ` jigsaw [this message]
2014-02-17 16:41 ` Stephen Hemminger
2014-02-17 17:52 ` Venkatesan, Venky
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=CAHVfvh4-KNT8EaGZ_HZaWwYEZ45QD3DO1znYZEXMO0Dy_Aiceg@mail.gmail.com \
--to=jigsaw@gmail.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).