From: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
To: "1534057243@qq.com" <1534057243@qq.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] 回复:RE: Thread safety in rte_acl
Date: Mon, 8 Jan 2018 13:06:54 +0000 [thread overview]
Message-ID: <682698A055A0F44AA47192B20141149765FECB13@BGSMSX102.gar.corp.intel.com> (raw)
In-Reply-To: <tencent_4138130D181E8DF66B214CD2D358C4559506@qq.com>
You can look at the source of anyone of the applications in samplevnf project in OPNFV which uses the active/shadow method for dynamically modifying the rules and applying them.
Regards
Kannan Babu
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ????
Sent: Monday, January 8, 2018 5:30 PM
To: Ananyev, Konstantin <konstantin.ananyev@intel.com>; dev <dev@dpdk.org>
Subject: [dpdk-dev] 回复:RE: Thread safety in rte_acl
>> 2. Is it safe that one
>> thread will run "rte_acl_classify" when another thread tries to add new rules to same ctx? thanks,
>Just add new rules is safe, but applying them (calling rte_acl_build()) is not.
In my case, there are two process sharing hugepage memory(struct rte_acl_ctx), one process call 'rte_acl_build' to add and apply rule, another process call frequently 'rte_acl_classify' to match rule, does it need to add lock? if not, is there other method to implement this safely?
------------------ 原始邮件 ------------------
发件人: "Ananyev, Konstantin";<konstantin.ananyev@intel.com>;
发送时间: 2018年1月8日(星期一) 晚上7:42
收件人: "真我风采"<1534057243@qq.com>;"dev"<dev@dpdk.org>;
主题: RE: [dpdk-dev] Thread safety in rte_acl
>
> Hi, I have two questions : 1. Is it safe that multiple threads will run "rte_acl_classify" in parallel (on the same ctx )?
Yes.
> 2. Is it safe that one
> thread will run "rte_acl_classify" when another thread tries to add new rules to same ctx? thanks,
Just add new rules is safe, but applying them (calling rte_acl_build()) is not.
Konstantin
next prev parent reply other threads:[~2018-01-08 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 5:42 [dpdk-dev] " =?gb18030?B?1ebO0rfnssk=?=
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 ` Ramia, Kannan Babu [this message]
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=682698A055A0F44AA47192B20141149765FECB13@BGSMSX102.gar.corp.intel.com \
--to=kannan.babu.ramia@intel.com \
--cc=1534057243@qq.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).