[P4-dev] Binding a table to an interface

Ganesh C S ch.sa.ganesh at gmail.com
Tue Jan 16 01:32:24 EST 2018


Having a global table with interface identifier looks to be a hack.

Some routers have separate ingress that can be populated with locally
relevant logic. I am looking for p4 equivalent of this.

regs
Ganesh

On Sun, Jan 14, 2018 at 5:21 AM, Hardik Soni <hardik.soni at inria.fr> wrote:

> put InControl.inputPort as a match field for the tables.
>
> -Hardik
>
> ------------------------------
>
> *From: *"Ganesh C S" <ch.sa.ganesh at gmail.com>
> *To: *p4-dev at lists.p4.org
> *Sent: *Sunday, 14 January, 2018 12:16:06 PM
> *Subject: *[P4-dev] Binding a table to an interface
>
>
> Hi,
>
> I am new to P4 and am trying to bind specific match-action tables to
> interfaces. In my case, a packet received on ingress interface A, it should
> look at table A. Similarly, ingress interface B should look at table B and
> so on.
>
> Any way of binding the tables to the interfaces ?
>
> regs
> Ganesh
>
> _______________________________________________
> P4-dev mailing list
> P4-dev at lists.p4.org
> http://lists.p4.org/mailman/listinfo/p4-dev_lists.p4.org
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p4.org/pipermail/p4-dev_lists.p4.org/attachments/20180115/aa131861/attachment-0002.html>


More information about the P4-dev mailing list