[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y32ifmug.fsf@toke.dk>
Date: Mon, 03 Jun 2019 22:14:15 +0200
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Kevin Darbyshire-Bryant <ldir@...byshire-bryant.me.uk>,
ldir@...byshire-bryant.me.uk
Cc: netdev@...r.kernel.org, stephen@...workplumber.org
Subject: Re: [PATCH RFC iproute2-next v4] tc: add support for action act_ctinfo
Kevin Darbyshire-Bryant <ldir@...byshire-bryant.me.uk> writes:
> ctinfo is an action restoring data stored in conntrack marks to various
> fields. At present it has two independent modes of operation,
> restoration of DSCP into IPv4/v6 diffserv and restoration of conntrack
> marks into packet skb marks.
>
> It understands a number of parameters specific to this action in
> additional to the usual action syntax. Each operating mode is
> independent of the other so all options are optional, however not
> specifying at least one mode is a bit pointless.
>
> Usage: ... ctinfo [dscp mask [statemask]] [cpmark [mask]] [zone ZONE]
> [CONTROL] [index <INDEX>]
>
> DSCP mode
>
> dscp enables copying of a DSCP store in the conntrack mark into the
> ipv4/v6 diffserv field. The mask is a 32bit field and specifies where
> in the conntrack mark the DSCP value is stored. It must be 6 contiguous
> bits long, e.g. 0xfc000000 would restore the DSCP from the upper 6 bits
> of the conntrack mark.
>
> The DSCP copying may be optionally controlled by a statemask. The
> statemask is a 32bit field, usually with a single bit set and must not
> overlap the dscp mask. The DSCP restore operation will only take place
> if the corresponding bit/s in conntrack mark yield a non zero result.
>
> eg. dscp 0xfc000000/0x01000000 would retrieve the DSCP from the top 6
> bits, whilst using bit 25 as a flag to do so. Bit 26 is unused in this
> example.
>
> CPMARK mode
>
> cpmark enables copying of the conntrack mark to the packet skb mark. In
> this mode it is completely equivalent to the existing act_connmark.
> Additional functionality is provided by the optional mask parameter,
> whereby the stored conntrack mark is logically anded with the cpmark
> mask before being stored into skb mark. This allows shared usage of the
> conntrack mark between applications.
>
> eg. cpmark 0x00ffffff would restore only the lower 24 bits of the
> conntrack mark, thus may be useful in the event that the upper 8 bits
> are used by the DSCP function.
>
> Usage: ... ctinfo [dscp mask [statemask]] [cpmark [mask]] [zone ZONE]
> [CONTROL] [index <INDEX>]
> where :
> dscp MASK is the bitmask to restore DSCP
> STATEMASK is the bitmask to determine conditional restoring
> cpmark MASK mask applied to restored packet mark
> ZONE is the conntrack zone
> CONTROL := reclassify | pipe | drop | continue | ok |
> goto chain <CHAIN_INDEX>
>
> Signed-off-by: Kevin Darbyshire-Bryant <ldir@...byshire-bryant.me.uk>
>
> ---
> v2 - fix whitespace issue in pkt_cls
> fix most warnings from checkpatch - some lines still over 80 chars
> due to long TLV names.
> v3 - fix some dangling else warnings.
> refactor stats printing to please checkpatch.
> send zone TLV even if default '0' zone.
> now checkpatch clean even though I think some of the formatting
> is horrible :-)
> sending via google's smtp 'cos MS' exchange office365 appears
> to mangle patches from git send-email.
> v4 - use the NEXT_ARG macros throughout.
> fix printing typo use 'cpmark' instead of 'mark'.
> use space separator between dscp mask & optional statemask and
> update usage as a result.
> validate dscp mask & statemask and print friendlier warnings
> than "invalid".
> fix cpmark option default value handling bug.
No further comments on this version; you should probably re-submit
without the RFC tag, though.
Feel free to add my
Reviewed-by: Toke Høiland-Jørgensen <toke@...hat.com>
when you do...
-Toke
Powered by blists - more mailing lists