From: =?gb18030?B?1ebO0rfnssk=?= <1534057243@qq.com>
To: =?gb18030?B?ZGV2?= <dev@dpdk.org>
Subject: [dpdk-dev] Thread safety in rte_acl
Date: Mon, 8 Jan 2018 13:42:14 +0800 [thread overview]
Message-ID: <tencent_E2344D391E89B644E164D2C018C3959BB806@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 246 bytes --]
Hi, I have two questions : 1. Is it safe that multiple threads will run "rte_acl_classify" in parallel (on the same ctx )? 2. Is it safe that one thread will run "rte_acl_classify" when another thread tries to add new rules to same ctx? thanks,
next reply other threads:[~2018-01-08 5:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 5:42 =?gb18030?B?1ebO0rfnssk=?= [this message]
2018-01-08 11:42 ` Ananyev, Konstantin
2018-01-08 11:59 ` [dpdk-dev] =?gb18030?b?u9i4tKO6UkU6ICBUaHJlYWQgc2FmZXR5IGluIHJ0?= =?gb18030?q?e=5Facl?= =?gb18030?B?1ebO0rfnssk=?=
2018-01-08 12:17 ` [dpdk-dev] 回复：RE: Thread safety in rte_acl Ananyev, Konstantin
2018-01-08 13:43 ` [dpdk-dev] =?gb18030?b?u9i4tKO6UkU6ILvYuLSjulJFOiAgVGhyZWFkIHNh?= =?gb18030?q?fety_in_rte=5Facl?= =?gb18030?B?1ebO0rfnssk=?=
2018-01-10 2:50 ` =?gb18030?B?1ebO0rfnssk=?=
2018-01-10 4:00 ` [dpdk-dev] 回复：RE: 回复：RE: Thread safety in rte_acl Ramia, Kannan Babu
2018-01-10 11:46 ` Ananyev, Konstantin
2018-01-15 2:01 ` [dpdk-dev] =?gb18030?b?u9i4tKO6UkU6ILvYuLSjulJFOiC72Li0o7pSRTog?= =?gb18030?q?_Thread_safety_in_rte=5Facl?= =?gb18030?B?1ebO0rfnssk=?=
2018-01-15 10:34 ` [dpdk-dev] 回复：RE: 回复：RE: 回复：RE: Thread safety in rte_acl Ananyev, Konstantin
2018-01-15 10:41 ` [dpdk-dev] =?gb18030?b?u9i4tKO6UkU6ILvYuLSjulJFOiC72Li0o7pSRTogu9i4tKO6UkU6ICBUaHJlYWQgc2FmZXR5IGluIHJ0ZV9hY2w=?= =?gb18030?B?1ebO0rfnssk=?=
2018-01-08 13:06 ` [dpdk-dev] 回复：RE: Thread safety in rte_acl Ramia, Kannan Babu
2018-01-08 13:42 ` [dpdk-dev] =?gb18030?b?u9i4tKO6UkU6ICC72Li0o7pSRTogIFRocmVhZCBz?= =?gb18030?q?afety_in_rte=5Facl?= =?gb18030?B?1ebO0rfnssk=?=
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=tencent_E2344D391E89B644E164D2C018C3959BB806@qq.com \
--to=1534057243@qq.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).