From: "Lilijun (Jerry)" <jerry.lilijun@huawei.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: [dpdk-stable] Question about rte_hash ext flags on mulitithread read/write
Date: Thu, 5 Mar 2020 02:01:18 +0000 [thread overview]
Message-ID: <40280F65B1B0B44E8089ED31C01616EBA48C5236@dggeml529-mbx.china.huawei.com> (raw)
Hi All,
There is some description about RTE hash's multi-thread support in Programmer's Guide. After reading that I still have some questions as follows:
1) There is a sentence " In all modes of operation lookups are thread-safe meaning lookups can be called from multiple threads concurrently.".
But if the extra_flag is only set RTE_HASH_EXTRA_FLAGS_EXT_TABLE, RTE hash will use a link list to store extend buckets due to excessive hash collisions.
So how can we make sure the link list accesses are safe with reading/writing concurrently?
2) Can we support multithread writing with RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF being set? Do we need add RTE_HASH_EXTRA_FLAGS_MULTI_WRITER_ADD flag?
Any reply will be appreciated very much. Thanks.
Jerry
reply other threads:[~2020-03-05 2:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40280F65B1B0B44E8089ED31C01616EBA48C5236@dggeml529-mbx.china.huawei.com \
--to=jerry.lilijun@huawei.com \
--cc=dev@dpdk.org \
--cc=stable@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).