DPDK usage discussions
 help / color / mirror / Atom feed
From: Rob Zimmerman <rob@thezims.net>
To: users@dpdk.org
Subject: [dpdk-users] Is Elastic Flow Distributor thread-safe?
Date: Mon, 13 Feb 2017 09:26:23 -0500	[thread overview]
Message-ID: <CAG0K5qvb_pV7Z8N=gNw+JiSjvq3CfF=t1EALhHaJ_PxSTGKE5Q@mail.gmail.com> (raw)

Hi Everyone,

  Playing around with EFD and seeing some really bizarre behavior in a
multi-core environment. Is it safe for multiple logical cores to be making
EFD table updates while another logical core is performing lookups? Side
note: the core which is making lookups is where the offline table resides.

Intuition tells me this is probably not safe, but the docs make no mention
of thread safety.

Thanks,
-Rob

             reply	other threads:[~2017-02-13 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 14:26 Rob Zimmerman [this message]
2017-02-14 14:14 ` De Lara Guarch, Pablo
2017-02-14 14:23   ` Rob Zimmerman
2017-02-14 14:26   ` Thomas Monjalon
2017-02-14 14:38     ` De Lara Guarch, Pablo

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='CAG0K5qvb_pV7Z8N=gNw+JiSjvq3CfF=t1EALhHaJ_PxSTGKE5Q@mail.gmail.com' \
    --to=rob@thezims.net \
    --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).