[P4] Fwd: Re: [P4-design] P4_14 changes

[Sándor Laki]

-------- Forwarded Message --------
Subject: 	Re: [P4-design] P4_14 changes
Date: 	Tue, 27 Sep 2016 23:11:11 -0700
From: 	Changhoon Kim <chang at barefootnetworks.com>
To: 	p4-design at lists.p4.org <p4-design at lists.p4.org>
CC: 	Amin Vahdat <vahdat at google.com>



Team,

We haven't had time to discuss these changes at our last meeting. 
Gordon, Peter, and a few other told me they're in favor of these 
tidying-up changes for P4_14. Please give me a holler in a day or two if 
you oppose to these. Otherwise, I'll publish these changes via P4.org 
late Friday.

Thanks.

-- Chang

On Thu, Sep 22, 2016 at 10:03 AM, Peter Newman (petenewm) 
<petenewm at cisco.com <mailto:petenewm at cisco.com>> wrote:

    Chang,

    Thanks for tidying this up. I had noticed that the primitive actions
    in switch.p4 did not exactly agree with the spec. This looks fine.

    —Peter


    On Sep 20, 2016, at 6:11 PM, Changhoon Kim
    <chang at barefootnetworks.com <mailto:chang at barefootnetworks.com>> wrote:

    Hi P4 designers,

    While we're all working busily to review the P4_16 proposal and
    trying to solidify it, I'd like to make a couple proposals related
    to a completely different topic: P4_14.

    1) The currently widely adopted P4_14 spec is the v1.0.2 version.
    All the public p4lang code out there is largely based on this spec,
    and I expect that this version will continue to be used for a while,
    as we'll phase into P4_16. Unfortunately there are a few minor
    discrepancies between the v1.0.2 spec and what's actually
    implemented in p4lang/p4-hlir and BMv2, causing confusion to P4
    beginners and writers right now. I think it'll be very helpful for
    the P4 community if we fix those discrepancies quickly. The attached
    draft -- which is tentatively versioned v1.0.3, but could be
    officially named P4_14 -- is an attempt to fix those issues. The
    extent of change is minimal, and the following list summarizes it.
    There's a revision history in the Appendix as well. I suggest we
    review this version quickly and publish it, replacing the v1.0.2 spec.

      * Page 29: removed register layout in register declaration.
      * removed bracket-based register referencing from
          o the parameters of modify_field, add_to_field and add primitives
      * Page 27, Section 7 intro.
      * Page 47, 9.1.2 Parameter Binding
      * page 87, example code: Use register_read/write primitives instead.

  # page 32: fixed execute_meter, modify_field_with_hash_based_offset,
    added register_read/write
  # pages 37: fixed the name, description and parameter ordering of
    modify_field_with_hash_based_offset.
  # pages 40, 41: fixed execute_meter and added register_read/write
    primitives.
  # Changed optional parameters of push, pop, resubmit, recirculate,
    clone_* primitives to mandatory parameters. Revised pop/push
    descriptions accordingly.
    2) The v1.1 spec is currently in a pre-release review state. It
    hasn't gotten much traction, and we weren't able to secure the
    necessary code contributions that fully realize this version either.
    Meanwhile P4_16 offers language features addressing all the goals we
    wanted to achieve with v1.1, including extern types, stronger type,
    expression support, etc., and even more. Given that we'll publish
    P4_16 soon, I suggest we withdraw the v1.1 spec. That way, we'll
    avoid proliferation of spec variations and minimize confusion.

    Let me know your thought on this. If there's no strong objection,
    I'll go ahead and make these changes by next week.

    Thanks.

    -- Chang


    <p4_14_v1.0.3-draft.pdf>_______________________________________________
    P4-design mailing list
    P4-design at lists.p4.org <mailto:P4-design at lists.p4.org>
    http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org
    <http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org>





---
Ezt az e-mailt az Avast víruskereső szoftver átvizsgálta.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://plc.inf.elte.hu/pipermail/p4/attachments/20160928/d778318e/attachment.html>
-------------- next part --------------
_______________________________________________
P4-design mailing list
P4-design at lists.p4.org
http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org