[P4-design] Early draft design document for a P4 module system
hemant at mnkcg.com
hemant at mnkcg.com
Mon May 20 10:54:33 EDT 2019
It may be early for the document, but a module should support updating the parser graph when module B merges with module A. At the least, module A calls module B’s parser from a specific node in module A’s parsed graph. Likewise, should we allow module B modifying a module A’s header/struct?
From: P4-design <p4-design-bounces at lists.p4.org> On Behalf Of Andy Fingerhut (jafinger) via P4-design
Sent: Sunday, May 19, 2019 7:59 PM
To: Andy Fingerhut (jafinger) via P4-design <p4-design at lists.p4.org>
Subject: Re: [P4-design] Early draft design document for a P4 module system
Just a reminder about this May 20, 2019 meeting of the P4 language design work group, 1:30-3pm Pacific time. Details for joining the meeting are at the bottom of the message below.
Several people have read and commented on the draft document describing questions about the design of a P4 module system, here:
Anyone should be able to read it. If you would like to make comments on it, but do not have permission to do so, please reply privately to me and I should be able to add permission for you.
From: "Andy Fingerhut (jafinger)" <jafinger at cisco.com <mailto:jafinger at cisco.com> >
Date: Monday, May 13, 2019 at 5:33 PM
To: "Andy Fingerhut (jafinger) via P4-design" <p4-design at lists.p4.org <mailto:p4-design at lists.p4.org> >
Cc: "Andy Fingerhut (jafinger)" <jafinger at cisco.com <mailto:jafinger at cisco.com> >
Subject: Early draft design document for a P4 module system
This document is still in very early draft stage, and probably months away from inclusion in the P4_16 language specification, at the soonest.
The intent is to get something down on digital paper to discuss, vs. brainstorming over a blank page. While writing up this document, I have thought of many questions, some of which I have proposed answers to in the document. I fully expect others will have good answers to consider, too.
There is a meeting of the LDWG scheduled 1:30-3pm Pacific time on Monday, May 20, 2019. You can check the P4.org calendar of events for the invitation, and I have copied the info for joining the meeting at the bottom of this message.
Anyone should be able to read the document at this link: https://docs.google.com/document/d/1NNC4t5NjAhzOhiC_DauiYrw80h1cXjZhshdRTuAPSnc/edit?usp=sharing
As far as I know, we do not already have a Google Docs folder for P4.org documents that all members have permission to comment on and/or edit. I have sent invitations to about 15 to 20 people for this document giving them permission to add comments and edit (please be generous with your comments, and cautious with your edits).
If you would like to add comments on the Google Doc itself, please reply privately to me asking for permission, and I can grant it to you. I haven’t tried to exclude anyone – it is just a very tedious task to give explicit permission to all members of this and other P4.org email lists. Feel free to pass this message on to anyone you think may be interested.
Monday, May 20, 2019
1:30-3:00pm Pacific time
+1 669 900 6833 or +1 646 558 8656
Meeting ID: 212 542 346
We are proposing the following schedule for the P4 language design meetings: a regular meeting on the first Monday of every month; this will be rescheduled to the second Monday if the first Monday is a holiday. We may have additional meetings on other Mondays with sub-working groups that are interested in advancing particular language issues, e.g., as we had with the modularity working group.
Currently there is no physical location for the meeting; if someone wants to volunteer to host one please let us know.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the P4-design