On Tue, May 16, 2023 at 02:18:15PM +0300, Nikolay Aleksandrov wrote:
> On 16/05/2023 14:10, Vladimir Oltean wrote:
> > On Tue, May 16, 2023 at 02:04:30PM +0300, Nikolay Aleksandrov wrote:
> >> That was one of the questions actually. More that I'm thinking about this, the more
> >> I want to break it apart by type because we discussed being able to specify a flag
> >> mask for the limit (all, dynamic, dynamic+static etc). If we embed these stats into a
> >> bridge fdb count attribute, it can be easily extended later if anything new comes along.
> >> If switchdev doesn't support some of these global limit configs, we can pass the option
> >> and it can deny setting it later. I think this should be more than enough as a first step.
> >
> > Ok, and by "type" you actually mean the impossibly hard to understand
> > neighbor discovery states used by the bridge UAPI? Like having
>
> Yes, that is what I mean. It's not that hard, we can limit it to a few combinations
> that are well understood and defined.
>
> > (overlapping) limits per NUD_REACHABLE, NUD_NOARP etc flags set in
> > ndm->ndm_state? Or how should the UAPI look like?
>
> Hmm, perhaps for the time being and for keeping it simpler it'd be best if the type initially is just about
> dynamic entries and the count reflects only those. We can add an abstraction later if we want "per-type"/mask limits.
> Adding such abstraction should be pretty-straight forward if we keep in mind the flags that can change only
> under lock, otherwise proper counting would have to be revisited.
Now that I implemented most of v2, except that I kept the netlink API
roughly the same as v1, I noticed that we probably need to discuss the UAPI
design more, or else we'd be stuck with the new netlink attributes that
do not fit the later abstraction design.
I see several options from what was discussed here and what seems to be
the easiest to implement for me:
1. Everything is a separate netlink attribute:
My current draft of v2 adds 2 netlink attributes -
IFLA_BR_FDB_MAX_LEARNED_ENTRIES and IFLA_BR_FDB_CUR_LEARNED_ENTRIES.
More generally this would be two u32 netlink attributes for each limit
(_MAX_ (RW) and _CUR_ (RO)), which can be differentiated by their name.
1.a Each limit is a separate netlink attribute, _CUR_ and _MAX_ are
grouped together as a nested message:
Like 1., but add only one netlink attribute for each limit
(e.g. IFLA_BR_FDB_LIMIT_LEARNED), containing a nested message with the
_CUR_ and _MAX_ attributes.
1.b The same as 1.a, but have one nested message
(e.g. IFLA_BR_FDB_LIMITS):
The message would contain attributes of the form
IFLA_BR_FDB_LIMITS_${NAME}_CUR, IFLA_BR_FDB_LIMITS_${NAME}_MAX, initially
only for NAME=LEARNED.
2. Add a new dynamically sized list of attributes + flag mask:
Permitt the netlink caller to pass a dynamically sized array
(NL_ATTR_TYPE_NESTED_ARRAY?) of pairs of a flag (and state) mask
combination and the limit to enforce for them. We'd be rejecting
everything but NTF_USE + NUD_NOARP for the first implementation.
Problems:
- Those are the impossibly hard to understand neighbour discovery
states. (as in the quoted mail) Having now looked closer at them
and the bridge internal flags they translate to, I also would prefer
a different approach.
- For the general approach of not just rejecting all but one
flag combination accounting is more difficult.
For the one limit in v1, and the v2 draft, we can just start counting
when creating the bridge, and the accounting is up to date when the
user sets a limit.
For the general approach later we'd probably not want to include
separate counters for each combination in the bridge struct. Instead
we'd dynamically allocate our counter when the user sets a limit,
so for each newly set limit we'd then need to lock the fdb table and
count the current fdb entries matching the limit first.
2.a Invent new names for the supported limits without exposing their flag
(and state) masks:
Conceptually this is equivalent to putting the names in the netlink
attribute namespace as in 1., so I'd prefer to go with one of them
instead.
Do you have a preference for an approach from the list, or do you see
different options I did not include?
