DPDK usage discussions
 help / color / mirror / Atom feed
From: longtb5@viettel.com.vn
To: <users@dpdk.org>
Cc: <yipeng1.wang@intel.com>, <sameh.gobriel@intel.com>
Subject: [dpdk-users] Membership library thread safety
Date: Fri,  1 Jun 2018 14:09:46 +0700 (ICT)	[thread overview]
Message-ID: <012701d3f978$57d75d40$078617c0$@viettel.com.vn> (raw)

Hi, 

I'm using rte_member in my application. I have two questions.
1. Could a rte_member_setsum be initialized on one thread and used on
another thread?
2. Are the operations (lookup, add, reset,.) atomic, or do I need to use
some kind of locking (e.g. rte_spinlock)?

I couldn't find anything in the doc. My guess is that you can init and use a
setsum on different threads just fine, but sharing a setsum among different
threads does require locking.

Thanks and best regards,
-BL
 

             reply	other threads:[~2018-06-01  7:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01  7:09 longtb5 [this message]
     [not found] ` <D2C4A16CA39F7F4E8E384D204491D7A661454197@ORSMSX105.amr.corp.intel.com>
2018-06-11  9:41   ` longtb5

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='012701d3f978$57d75d40$078617c0$@viettel.com.vn' \
    --to=longtb5@viettel.com.vn \
    --cc=sameh.gobriel@intel.com \
    --cc=users@dpdk.org \
    --cc=yipeng1.wang@intel.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).