[P4-dev] 2 questions

Garegin Grigoryan grigorg at clarkson.edu
Mon Jun 12 12:34:28 EDT 2017


1) Is this example is compatible with P4_16? 

It gives me an error (“could not find declaration for “clone_ingress_pkt_to_egress”")

Sincerely, 
Garegin Grigoryan
grigorg at clarkson.edu

> On Jun 8, 2017, at 2:42 AM, Nate Foster <jnfoster at cs.cornell.edu> wrote:
> 
> 1) You can see an example of packet cloning here: 
> https://github.com/p4lang/switch/blob/21d750ce6015c54978ee9a3519838340698876c7/p4src/sflow.p4#L69 <https://github.com/p4lang/switch/blob/21d750ce6015c54978ee9a3519838340698876c7/p4src/sflow.p4#L69>
> https://github.com/p4lang/switch/blob/135599947d53d7dc2f830b12f4e169f430d78af0/p4src/acl.p4 <https://github.com/p4lang/switch/blob/135599947d53d7dc2f830b12f4e169f430d78af0/p4src/acl.p4>
> 
> 2) See the P4 tutorial slides, starting around page 91, for a description of the "PD" API.
> https://github.com/p4lang/tutorials/blob/master/SIGCOMM_2016/p4-tutorial-slides.pdf <https://github.com/p4lang/tutorials/blob/master/SIGCOMM_2016/p4-tutorial-slides.pdf> 
> 
> -N
> 
> On Sun, Jun 4, 2017 at 1:08 PM, Garegin Grigoryan <grigorg at clarkson.edu <mailto:grigorg at clarkson.edu>> wrote:
> Thank you!
> 
> 1) Could you give a code example (or a reference) for P4_16 standard regarding packet cloning?
> 2) What kind of control plane API for bmv2 model is available?
> 
> 
> On Fri, Jun 2, 2017 at 2:21 PM, Nate Foster <jnfoster at cs.cornell.edu <mailto:jnfoster at cs.cornell.edu>> wrote:
> 1) Is it possible to clone packets at the data plane and forward a cloned packet through the pipeline to the egress and then output it?
> 
> Yes, although the details of how cloning works are architecture specific.
>  
> 2) How can I print the contents of a table and registers in P4?
> 
> You need to write a program against the control-plane API for your P4 program to do this.
> 
> -N
> 
> 
> 
> -- 
> Sincerely,
> Garegin Grigoryan
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p4.org/pipermail/p4-dev_lists.p4.org/attachments/20170612/5424640c/attachment-0002.html>


More information about the P4-dev mailing list