Rare project developers

[mc36 <>]

hi,
sounds cool... i also did some of my homework with the optimizer...
now it accepts arbitrary p4c parameters after the profile.tmpl name, that 
will be passed...
(i also updated the .sh files to have the previous functionality...)

for curiosity i reoptimized the p profile and the difference speaks for 
itself:
mc36@noti:~$ diff profile-p.old profile-p.p4
18c18
< #define IPV4_LPM_TABLE_SIZE            65536
---
> #define IPV4_LPM_TABLE_SIZE            417385
20c20
< #define IPV6_LPM_TABLE_SIZE            16384
---
> #define IPV6_LPM_TABLE_SIZE            104346
28c28
< #define MPLS_TABLE_SIZE                163840
---
> #define MPLS_TABLE_SIZE                138106

so please consider running a full reoptimization round for both t1 and t2 
chips
because for now, the optimizer also works a bit differently on t1 too...

another idea, you support now onie_machine=model in /etc/machine.conf
please consider splitting it to two... let's say model_veth where the current
functionality would be exposed, and model_ext where you dont spin up the veth
creation but start with an external port map exposing the vm physical 
interfaces...
this way one could drop the image to gns3 and surround it with other boxes...
this is how i start my dataplane vm:
https://github.com/rare-freertr/freeRtr/blob/master/misc/p4bf/r1.sh
https://github.com/rare-freertr/freeRtr/blob/master/misc/p4bf/r2.sh
https://github.com/rare-freertr/freeRtr/blob/master/misc/p4bf/ports.json

thanks,
cs





On 6/3/22 15:40, Alexander Gall wrote:
> It's basically done, at least for a first go. All important features
> are there, I think. Just one annoying thing left to fix. The Tofino2
> SDE has a bug in the BFRT code that's harmless but generates so many
> error messages that I can't release it like that (the bug was reported
> on the Forum and Vladimir has assigned JIRA issue DRV-6313 to it). I'm
> going to write a patch that eliminates the messages next week. Then
> I'll test the ONIE installer and finally I'll make RARE release #2,
> hopefully also next week.
>
> Stay tuned :)