From: Tom Barbette <barbette@kth.se>
To: dpdk-dev <dev@dpdk.org>
Cc: Yipeng Wang <yipeng1.wang@intel.com>,
Sameh Gobriel <sameh.gobriel@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] Efficient deletion in rte_hash
Date: Wed, 27 Jan 2021 15:59:09 +0100 [thread overview]
Message-ID: <204cd192-8aa2-84d9-605b-41fa8f105351@kth.se> (raw)
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
Hi all,
In an ageing scenario, is there a faster way than calling
rte_hash_del_key() to delete an entry when we have the position (the
result of rte_hash_lookup()) on hand?
Particularly, with and without CONCURRENCY_LF set.
For instance, is it correct to call rte_hash_free_key_with_position()
with the position (the result of rte_hash_lookup())? I guess not.
Thanks,
Tom
reply other threads:[~2021-01-27 14:59 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=204cd192-8aa2-84d9-605b-41fa8f105351@kth.se \
--to=barbette@kth.se \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=sameh.gobriel@intel.com \
--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).