DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shyam Sundar Govindaraj <ssgovind@Brocade.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK LPM table thread safety
Date: Thu, 21 May 2015 17:51:34 +0000	[thread overview]
Message-ID: <ae4bd518eba943849e2a17d7f0aa5d63@BRMWP-EXMB11.corp.brocade.com> (raw)

Hi

  I am interested in DPDK LPM implementation. I understand the high performance of this LPM table but, when it comes to multithreaded application, I read the following safety issue in DPDK documentation. I understand that multithread read and multithread write are not possible without locking table. But I want to know if single thread write and multithread read are possible with your implementation without any locking mechanism.

20. Thread Safety of DPDK Functions
"The hash and LPM libraries are, by design, thread unsafe in order to maintain performance. However, if required the developer can add layers on top of these libraries to provide thread safety. Locking is not needed in all situations, and in both the hash and LPM libraries, lookups of values can be performed in parallel in multiple threads. Adding, removing or modifying values, however, cannot be done in multiple threads without using locking when a single hash or LPM table is accessed. Another alternative to locking would be to create multiple instances of these tables allowing each thread its own copy".
http://dpdk.org/doc/guides/prog_guide/thread_safety_intel_dpdk_functions.html

Thanks
Shyam

             reply	other threads:[~2015-05-21 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 17:51 Shyam Sundar Govindaraj [this message]
2015-05-22 13:55 ` Bruce Richardson

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=ae4bd518eba943849e2a17d7f0aa5d63@BRMWP-EXMB11.corp.brocade.com \
    --to=ssgovind@brocade.com \
    --cc=dev@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).