From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
Nidhia Varghese <nidhiavarghese93@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] Fwd: Sharing tables among pipelines
Date: Tue, 9 May 2017 16:28:02 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912652798F27@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <54CBAA185211B4429112C315DA58FF6D31B5F93E@IRSMSX103.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Singh, Jasvinder
> Sent: Monday, May 8, 2017 11:37 AM
> To: Nidhia Varghese <nidhiavarghese93@gmail.com>; dev@dpdk.org;
> users@dpdk.org
> Subject: Re: [dpdk-dev] Fwd: Sharing tables among pipelines
>
> Hi Nidhia,
>
>
> For my pipeline application, I want to share same table between two
> different pipeline. Is that possible? If yes, how can I do it?
>
This is usually a bad idea due to the implications: locks required for each table record, performance penalty due to cache line ping-pong between cores.
See link below for a quick discussion:
http://www.dpdk.org/doc/guides/prog_guide/packet_framework.html#shared-data-structures
Usually we split the application-level table into several smaller tables that are sections of the big table and each one is handled by a different pipeline instance (of e.g. the flow classification pipeline type), with each instance potentially running on different CPU core; we make sure that packets reach the right pipeline instance through flow affinity schemes like RSS or SW steering.
> [Jasvinder] - In the current ip pipeline application, we don’t have such
> illustration of sharing a table between two pipelines. Therefore, you need to
> tweak the code to implement it for your application.
>
> Thanks,
> Jasvinder
next prev parent reply other threads:[~2017-05-09 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 10:13 [dpdk-users] " Nidhia Varghese
2017-05-08 4:54 ` [dpdk-users] Fwd: " Nidhia Varghese
2017-05-08 5:31 ` [dpdk-users] " zhilong zheng
2017-05-08 8:36 ` [dpdk-users] [dpdk-dev] Fwd: " Singh, Jasvinder
2017-05-09 16:28 ` Dumitrescu, Cristian [this message]
2017-05-09 17:59 ` Nidhia Varghese
2017-05-10 16:13 ` Shyam Shrivastav
2017-05-16 10:12 ` Dumitrescu, Cristian
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=3EB4FA525960D640B5BDFFD6A3D8912652798F27@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=nidhiavarghese93@gmail.com \
--cc=users@dpdk.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).