From bdc0e6b7204ea0211d4f7881497e4306586fb9ef Mon Sep 17 00:00:00 2001 From: Paul Vinciguerra Date: Sat, 22 Sep 2018 05:32:50 -0700 Subject: Trivial: Clean up some typos. Change-Id: I085615fde1f966490f30ed5d32017b8b088cfd59 Signed-off-by: Paul Vinciguerra --- src/plugins/acl/acl_lookup_context.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/plugins/acl/acl_lookup_context.md') diff --git a/src/plugins/acl/acl_lookup_context.md b/src/plugins/acl/acl_lookup_context.md index 53ad1ef0e46..e95f82043f9 100644 --- a/src/plugins/acl/acl_lookup_context.md +++ b/src/plugins/acl/acl_lookup_context.md @@ -8,7 +8,7 @@ However, some uses outside of pure traffic control have appeared, for example, ACL-based forwarding, etc. Also, improved algorithms of the ACL lookup could benefit of the more abstract representation, not coupled to the interfaces. -This describes a way to accomodate these use cases by generalizing the ACL +This describes a way to accommodate these use cases by generalizing the ACL lookups into "ACL lookup contexts", not tied to specific interfaces, usable by other portions of the code by utilizing the exports.h header file, which provides the necessary interface. @@ -21,7 +21,7 @@ The first reason is the logical grouping of multiple ACLs. The interface matching code currently allows for matching multiple ACLs in a 'first-match' fashion. Some other use cases also fall into a similar -pattern: they attemt to match a sequence of ACLs, and the first matched ACL +pattern: they attempt to match a sequence of ACLs, and the first matched ACL determines what the outcome is, e.g. where to forward traffic. Thus, a match never happens on an ACL in isolation, but always on a group of ACLs. @@ -79,7 +79,7 @@ in the "show acl lookup context" command. To set the vector of ACL numbers to be looked up within the context, use the function acl_plugin.set_acl_vec_for_context(lc_index, acl_list). The first parameter specifies the context that you have created, the second parameter is a vector of u32s, each u32 being the index of the ACL -which we should be looking up within this context. The comand is idempotent, i.e. +which we should be looking up within this context. The command is idempotent, i.e. it unapplies the previously applied list of ACLs, and then sets the new list of ACLs. Subsequent ACL updates for the already applied ACLs will cause the re-application -- cgit 1.2.3-korg