[PATCH nft 2/2] src: store expression as set key instead of data type

Doing so retains legth information in case of unqualified data types, e.g. we now have 'meta iifname' expression instead of an (unqualified) string type. This allows to eventually use iifnames as set keys without adding yet another special data type for them. Signed-off-by: Florian Westphal

[PATCH nft 1/2] evaluate: prepare to store expr key rather than datatype

currently set definitions store a datatype rather than an expression. In order to support use of unqualified data types (string in particular), this prepares implicit set definition helper to expect an expression instead of plain data type. This also has the advantage that we can use EXPR_CONCAT

Re: [ulogd2 PATCH] ulogd: use a RT scheduler by default

On 7 September 2017 at 13:36, Arturo Borrero Gonzalez wrote: > Is common that ulogd runs in scenarios where a lot of packets are to be > logged. > If there are more packets than ulogd can handle, users can start seing log > messages like this: > > ulogd[556]: We are losing