<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello Olivier,</p>
<p><br>
</p>
<p>This is very, very interesting. I'll take a look at that.</p>
<p><br>
</p>
<p>Thank you,</p>
<p>-ŁW</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 21-Jan-19 18:25,
<a class="moz-txt-link-abbreviated" href="mailto:olivier.dugeon@orange.com">olivier.dugeon@orange.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:28218_1548091548_5C46009C_28218_458_1_d52e2b0a-62dc-0c18-0d80-8f49dbd38a8e@orange.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><font face="DejaVu Sans">Hello Lukasz</font></p>
<p>We, in our lab, are looking to such approach.</p>
<p>After looking to various project (Open Network Linux,
OpenSwitch and Sonic), I understand that the best is to use
OpenSAI library (Switch Abstraction Interface). OpenSwith and
Sonic are using this approach. Then, FRRouting is running a
usual pushing into the kernel FIB entries. Another daemon is
listen to any modification done to the Kernel FIB and
automatically transmit the modification to the ASIC through
OpenSAI.</p>
<p>You could have a look at OpenSwith documentation here: <a
moz-do-not-send="true"
href="https://github.com/open-switch/opx-docs/wiki/Layer-3">https://github.com/open-switch/opx-docs/wiki/Layer-3</a>
as an example.</p>
<p>The other approach consist to use the FPM interface of
FRRouting to directly talk to the ASIC. However, if this
approach could be more efficient, it is very hard to develop and
need to be adapted to each ASIC family. In fact, the goal of
OpenSAI library is to unify the different ASIC vendor API which
overcome this problem. Now, we could question if there is an
opportunity to develop an OpenSAI / FPM converter. Not sure if
it is pertinent. We are continuing our investigation evaluating
OpenSwitch and SONIC as well as looking how both project use
OpenSAI.<br>
</p>
<p>Regards</p>
<p>Olivier<br>
</p>
<br>
<div class="moz-cite-prefix">Le 21/01/2019 à 14:17, Łukasz Wójcik
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:%3C26d36902-6134-7fec-2804-7f0cc286ba0b@zoho.com%3E">
<pre wrap="">Hello there,
In the era of Open Networking equipment, e.g. switching ASICs support
forwarding based on L3 information. I was wondering,
if FRRouting supports or plans to support any mechanisms that would
allow for passing L3 data to the hardware, and therefore
offloading some work to the HW ? I would imagine some kind of API or
event-driven mechanisms that would require HW manufacturer's
SDKs/API to glue-to/plug-into FRRouting ?
Best regards,
-ŁW
</pre>
</blockquote>
<br>
<pre>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre>
</blockquote>
</body>
</html>