X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fprog_guide%2Fpacket_classif_access_ctrl.rst;h=a9a5815a126b9e714cd427893d5c80723702639f;hb=fea1d908d39989a27890b29b5c0ec94c85c8257b;hp=210b020790beb269f41c0b1a3450912252068653;hpb=9f0bf3f4a3eabd7ab5af13b4ed793c36e7615b35;p=dpdk.git diff --git a/doc/guides/prog_guide/packet_classif_access_ctrl.rst b/doc/guides/prog_guide/packet_classif_access_ctrl.rst index 210b020790..a9a5815a12 100644 --- a/doc/guides/prog_guide/packet_classif_access_ctrl.rst +++ b/doc/guides/prog_guide/packet_classif_access_ctrl.rst @@ -281,14 +281,14 @@ for each of them. Depending on the rule-set, it might reduce RT memory requirements but might increase classification time. There is a possibility at build-time to specify maximum memory limit for internal RT structures for given AC context. -It could be done via **max_size** field of the **rte_acl_config** strucure. +It could be done via **max_size** field of the **rte_acl_config** structure. Setting it to the value greater than zero, instructs rte_acl_build() to: -* attempt to minimise number of tries in the RT table, but +* attempt to minimize number of tries in the RT table, but * make sure that size of RT table wouldn't exceed given value. -Setting it to zero makes rte_acl_build() to use the default behaviour: -try to minimise size of the RT structures, but doesn't expose any hard limit on it. +Setting it to zero makes rte_acl_build() to use the default behavior: +try to minimize size of the RT structures, but doesn't expose any hard limit on it. That gives the user the ability to decisions about performance/space trade-off. For example: @@ -304,12 +304,12 @@ For example: * populated with rules AC context and cfg filled properly. */ - /* try to build AC context, with RT strcutures less then 8MB. */ + /* try to build AC context, with RT structures less then 8MB. */ cfg.max_size = 0x800000; ret = rte_acl_build(acx, &cfg); /* - * RT strcutures can't fit into 8MB for given context. + * RT structures can't fit into 8MB for given context. * Try to build without exposing any hard limit. */ if (ret == -ERANGE) {