store expression instead of data type as set key
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | evaluate: prepare to store expr key rather than datatypesrc/ | +23 | 1 reply | |
| 2/2 | src: store expression as set key instead of data typeinclude/ src/ src/ +5 more | +104 | 4 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Pablo Neira Ayuso |
|---|---|
| 1/2 | A-b |
| 2/2 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH nft 0/2] store expression instead of data type as set key
This is a prerequisite to later support dynamic data types, e.g. string, as a set key. The string datatype (and integer) do not have a fixed size, instead the size is determined by the expression.
This keeps the expression all the way down to set construction. Furthermore, in case of concatenations we can use EXPR_CONCAT to allow the netlink linearization step to determine the original sizes of the keys components.
Both changes are preparation work, they add no feature.