[dpdk-dev] =?gb18030?b?u9i4tKO6UkU6ICBUaHJlYWQgc2FmZXR5IGluIHJ0?= =?gb18030?q?e=5Facl?=

[=?gb18030?B?1ebO0rfnssk=?= <1534057243@qq.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 1141 bytes --]

>> 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