OK, thanks for the clarification. In my case rdomain IDs are sequentially generated and allocated, so this would be less of an issue with memory pressure. I believe the 255 limit could be on the low end if a larger fleet of nodes is factored in and say each tenant's identical rdomain IDs must potentially exist on every node. Jun 8, 2026, 11:40 by [email protected]:
> On Mon, Jun 08, 2026 at 10:13:44AM +0200, ptr wrote: > >> Hi misc, >> >> I've run into the maximum rdomain/rtable limit recently (255). Looks to >> be an 8bit field limitation. The virtual network model I am using atmo >> assigns interfaces with the rdomain ID being part of the interface name. >> > > No it is not. It is a limit to reduce memory pressure. > >> Example: rdomain 50, vport50, veb50. This logical naming works great for >> readability everywhere. >> The interface numbering can already scale well beyond 255. Would there >> be any appetite to grow the rdomain limit to at least a 16bit field? >> > > This is a dumb reason that wastes memory. When creating rdomain 50 the > system will allocate 48 unused slots. Which may be ok but then someone > comes up with rdomain 4000 for vlan4000. > > There may be a need for an extra lookup indirection but implementing is > not trivial. > -- > :wq Claudio >
