From: Shyam Shrivastav <shrivastav.shyam@gmail.com>
To: Nidhia Varghese <nidhiavarghese93@gmail.com>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.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: Wed, 10 May 2017 21:43:59 +0530 [thread overview]
Message-ID: <CAGSp03mVrj7wKQ3N-DTmiOrtA53sYsvf0EeazMC7dAXAQuWOig@mail.gmail.com> (raw)
In-Reply-To: <CAAx9ALXom4Xaa+Huwepk8ZHYJwRtczAZ6-DvGypBx0UxmMxEuQ@mail.gmail.com>
Something I have gathered reading through code if it helps, ip_pipeline is
designed such that user side cli (_fe) runs in master pipeline and sends
conf requests to various other packet processing pipelines (_be) which
handle such requests at intervals. These can run on same or different
threads(cores) as per conf, no locking requirement as table-updation &
table-reading (packet processing) always happens in same pipeline so always
same thread. Master pipeline can be configured to run on a separate core &
it should be the case, but table updation happens in pipeline thread only
at lower priority.
On Tue, May 9, 2017 at 11:29 PM, Nidhia Varghese <nidhiavarghese93@gmail.com
> wrote:
> Hi all,
>
> Thanks for your reply.
>
> As given in the link(3rd point), what I need is single writer
> thread(pipeline) performing table entry add/delete operations and another
> thread(which is in turn another pipeline) that performs lookup operations
> to the same table entries.
>
>
> Thanks,
> Nidhia Varghese
>
next prev parent reply other threads:[~2017-05-10 16:14 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
2017-05-09 17:59 ` Nidhia Varghese
2017-05-10 16:13 ` Shyam Shrivastav [this message]
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=CAGSp03mVrj7wKQ3N-DTmiOrtA53sYsvf0EeazMC7dAXAQuWOig@mail.gmail.com \
--to=shrivastav.shyam@gmail.com \
--cc=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).