tree 2e1cb4e1bd76e3320f13ebf7e37d5507dbf80a76
parent 8a0c6f84b4dfdd58a3bd89838b41a5b6c7843278
author developer <developer@mediatek.com> 1692869955 +0800
committer developer <developer@mediatek.com> 1693269994 +0800

[][openwrt][mt7988][pce][separate CLS entry definition from TOPS_ENTRY]

[Description]
Change CLS entry definition.

Before this patch modification, 1 CLS entry is strictly mapping to a
TOPS_ENTRY which means that 1 tunnel protocol can only occupy 1 CLS entry.
This implementation is based on the assumption of all tunnel protocols
separate different session by destination IP.

This may cause some problem if a tunnel protocol distinguish different
session not by destination IP.

Take IPsec ESP for instance, it use ESP header's SPI field to
differentiate sessions. In this example, ESP will occupy several CLS entry
for several sessions.

In this patch, CLS entry is not strictly mapped to 1 tunnel protocol
anymore.
If a protocol needs to use CLS to forward packets to HW offload engine,
the CLS configuration is now runtime configured instead of setup at boot
up.

Users can use mtk_pce_cls_entry_alloc() to allocate an empty cls_entry.
When they setup the cls_entry structure, they should use
mtk_pce_cls_entry_write() to write the CLS HW.

[Release-log]
N/A

Change-Id: I593be2075c8f27d247cda986ed324a6953a8fc13
Reviewed-on: https://gerrit.mediatek.inc/c/openwrt/feeds/mtk_openwrt_feeds/+/7923903