From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Arvind Narayanan <webguru2688@gmail.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Cc: "Wiles, Keith" <keith.wiles@intel.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] How to use software prefetching for custom structures to increase throughput on the fast path
Date: Wed, 12 Sep 2018 08:22:35 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA65E2C7A1A@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <CAHJJQSXNaV7ixaTTZzyaaXCiX7mtujgadyfZUxvtxKDu6hOwpQ@mail.gmail.com>
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Arvind Narayanan
> Sent: Tuesday, September 11, 2018 7:39 PM
> To: stephen@networkplumber.org
> Cc: Wiles, Keith <keith.wiles@intel.com>; users@dpdk.org
> Subject: Re: [dpdk-users] How to use software prefetching for custom
> structures to increase throughput on the fast path
<snip>
> So, essentially, what I am doing is -- core 0 gets a burst of my_packet(s)
> from its pre-allocated mempool, and then (bulk) enqueues it into a
> rte_ring. Core 1 then (bulk) dequeues from this ring and when it access the
> data pointed by the ring's element (i.e. my_packet->tag1)
You say "Bulk" here. Are you using "bulk" or "burst"?
Burst: http://doc.dpdk.org/api/rte__ring_8h.html#aff58e6a47ea3dca494dd0391d11b38ea
Bulk: http://doc.dpdk.org/api/rte__ring_8h.html#ab8debfb458e927d559e7ce750048502d
Try using "burst" dequeue which will return the max number of packets available,
even if it is less than the size of the array you provided.
Bulk will fail to dequeue anything unless your threshold of MAX was reached,
which means that likely you'll stall the consumer core waiting until MAX, and
then playing catchup again.
<snip>
next prev parent reply other threads:[~2018-09-12 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 8:15 Arvind Narayanan
2018-09-11 14:20 ` Wiles, Keith
2018-09-11 15:42 ` Arvind Narayanan
2018-09-11 16:52 ` Wiles, Keith
2018-09-11 17:18 ` Arvind Narayanan
2018-09-11 18:07 ` Stephen Hemminger
2018-09-11 18:39 ` Arvind Narayanan
2018-09-11 19:12 ` Stephen Hemminger
2018-09-12 8:22 ` Van Haaren, Harry [this message]
2018-09-11 19:36 ` Pierre Laurent
2018-09-11 21:49 ` Arvind Narayanan
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=E923DB57A917B54B9182A2E928D00FA65E2C7A1A@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=keith.wiles@intel.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=webguru2688@gmail.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).