Packet matching rule to support the range was previously available in ODP as part of pmr create function but the same was removed after discussion since most of the existing HWs were not able to support the range function.
We can add this point to the ODP public call to have a detailed discussion on this topic. Regards, Bala Regards, Bala On 1 February 2016 at 15:04, huanggaoyang <huanggaoya...@huawei.com> wrote: > Range Match is a common case in packet classification process. > The current pmr rules only support exact value. Simply, if we create a pmr > with term ODP_PMR_TCP_SPORT and value 2048, > then only the packets from src-port:2048 will match it, while those from 2047 > or 2049 won't match. > In this patch, I added a new pmr term to support user defined Range Match > rule. > That means, user can create the rule with the min and max value of the > key(which is determined by offset+mask+val_size), > then packets with a key that satisfiy min<=key<=max will all match the rule. > > huanggaoyang (2): > linux-generic:classification: add a new pmr term to support range > match > linux-generic:classification:add test case for the pmr term > ODP_PMR_CUSTOM_RANGE > > include/odp/api/classification.h | 16 ++- > .../include/odp_classification_datamodel.h | 16 ++- > .../include/odp_classification_inlines.h | 37 +++++- > platform/linux-generic/odp_classification.c | 23 +++- > test/validation/classification/classification.h | 1 + > .../classification/odp_classification_test_pmr.c | 135 > ++++++++++++++++++++- > 6 files changed, 214 insertions(+), 14 deletions(-) > > -- > 1.9.1 > > > _______________________________________________ > lng-odp mailing list > lng-odp@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/lng-odp _______________________________________________ lng-odp mailing list lng-odp@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lng-odp
