<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Feladó:</b> P4-design <p4-design-bounces@lists.p4.org>, meghatalmazó: Calin Cascaval <cascaval@barefootnetworks.com><br>
<b>Elküldve:</b> 2017. április 10. 23:52:32<br>
<b>Címzett:</b> Nate Foster<br>
<b>Másolatot kap:</b> p4-design@lists.p4.org<br>
<b>Tárgy:</b> [P4-design] Meeting minutes (Re: 4/10 draft agenda)</font>
<div> </div>
</div>
<div>
<h2 class=""><br class="">
</h2>
<div class="">
<h2 class="">Language compatibility</h2>
<p class="">What do we say at the workshop about backward compatibility</p>
<p class=""> - multiple implementations put more pressure on keeping stable releases more stable</p>
<p class=""> - hard to make promises that we’re not breaking compatibility</p>
<p class=""> - make an effort to keep compatibility w/o actually promising </p>
<p class="">- do we limit the scope to P4_14/16? </p>
<p class="">- do we know what changes are coming that potentially break compatibility? </p>
<p class=""> - composability and modularity </p>
<p class=""> - control plane </p>
<p class="">- is there a threshold for changes?</p>
<h2 class="">PR 158 - Add table of allowed member types in headers, structs, and tuples</h2>
<ul class="">
<li class="">structs and tuples should behave the same – compiler non-conformant. tuples behave as listed, structs do not
</li><li class="">nesting? target restrictions on total size, etc. </li><li class="">varbit? only one allowed in a header. Computed as the difference between total size and the rest of the fields
</li><li class="">error vs. match_kind in structs? match_kind is pretty much always used only as a type for table matches, and thus there is no need to store in variables. </li></ul>
AI:<br class="">
<ul class="">
<li class="">Andy to update with rationale </li><li class="">update the table with header_union when approved (part of header_union PR)
</li></ul>
<h2 class="">Issue 150 - Global instances</h2>
<ul class="">
<li class="">impact on resource allocation and sharing </li><li class="">instantiations whether inline in a package decl or at top level should be the same
</li><li class="">instantiations should be done by either the program or the architecture. Should we restrict at one? Answers
</li><li class="">these tables/controls are not dead code, since the control plane can access them
</li><li class="">compiler should be careful to distinguish between control- and data-plane inlining. Control-plane inlining should behave as the control was not inlined.
</li><li class="">architecture dependent </li></ul>
<p class="">AI: add a note of clarification to the spec</p>
<h2 class="">Issue 138 - Require unambiguous names</h2>
<ul class="">
<li class="">multiple aliases and what order they apply?
<ul class="">
<li class="">annotations are applied in program order, the last one remains exposed and all others become hidden
</li><li class="">need clarification </li></ul>
</li><li class="">Chris: proposes replacing rename with alias (and globalrename with globalalias)
</li></ul>
<p class="">AI: Cole to introduce in the spec</p>
<h2 class="">Issue 151 - Action calls from parsers</h2>
<ul class="">
<li class="">we should add functions to parsers rather than hijacking actions which are part of the match-action abstraction (which parsers are not)
</li></ul>
<p class="">AI: add lambdas to the next version of the language</p>
<h2 class="">PR 127, Issue 124 - adds specification for table entries</h2>
<p class="">AI: PR approval</p>
<div class=""></div>
</div>
<div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="Apple-interchange-newline">
--</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
Thanks, Calin</div>
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Apr 10, 2017, at 12:20, Nate Foster <<a href="mailto:jnfoster@cs.cornell.edu" class="">jnfoster@cs.cornell.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">Here's a final agenda for today (with two additions from @jafingerhut and bumping header unions).</div>
<div class=""><br class="">
</div>
<div class="">-N</div>
<div class=""><br class="gmail-m_5201371115417210342gmail-m_5829737396568822684gmail-Apple-interchange-newline">
* Status and Roadmap [5 minutes]</div>
<div class=""><br class="">
</div>
<div class="">* Stability / Backwards Compatibility [10 minutes]</div>
<div class=""><br class="">
</div>
* P4 Types [10 minutes]<br class="">
<a href="https://github.com/p4lang/p4-spec/pull/158" target="_blank" class="">https://github.com/p4lang/p4-<wbr class="">spec/pull/158</a>
<div class=""><br class="">
</div>
<div class="">* Calling Actions from Parsers [10 minutes]</div>
<div class=""><a href="https://github.com/p4lang/p4-spec/issues/151" target="_blank" style="font-family:calibri,arial,helvetica,sans-serif" class="">https://github.com/<wbr class="">p4lang/p4-spec/issues/151</a><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">* Global Instances (Continued) [15 minutes]</div>
<div class=""><a href="https://github.com/p4lang/p4-spec/issues/150" target="_blank" class="">https://github.com/p4lang/p4-s<wbr class="">pec/issues/150</a><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">* Control-Plane Names (Continued) [15 minutes]<br class="">
</div>
<div class=""><a href="https://github.com/p4lang/p4-spec/issues/138" target="_blank" class="">https://github.com/p4lang/p4-s<wbr class="">pec/issues/138</a><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">* Table entries (Continued) [15 minutes]<br class="">
</div>
<div class=""><a href="https://github.com/p4lang/p4-spec/pull/127" target="_blank" class="">https://github.com/p4lang/p4-s<wbr class="">pec/pull/127</a><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">* Other business [10 minutes]</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Sun, Apr 9, 2017 at 4:38 PM, Nate Foster <span dir="ltr" class="">
<<a href="mailto:jnfoster@cs.cornell.edu" target="_blank" class="">jnfoster@cs.cornell.edu</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div class="">We meet again tomorrow from 1:30pm-3:00pm PT in Gates 260. We have a lot to discuss so I plan to start the meeting right at 1:30pm.</div>
<div class=""><br class="">
</div>
<div class="">A draft agenda is below. Please let me know if you have anything you'd like to add to it. I'll circulate a final version tomorrow morning.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Draft Agenda:</div>
<div class=""><br class="">
</div>
<div class="">* Status and Roadmap [5 minutes]</div>
<div class=""><br class="">
</div>
<div class="">* Stability / Backwards Compatibility [15 minutes]</div>
<div class=""><br class="">
</div>
<div class="">* Global Instances (Continued) [15 minutes]</div>
<div class=""><a href="https://github.com/p4lang/p4-spec/issues/150" target="_blank" class="">https://github.com/p4lang/p4-s<wbr class="">pec/issues/150</a><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">* Control-Plane Names (Continued) [15 minutes]<br class="">
</div>
<div class=""><a href="https://github.com/p4lang/p4-spec/issues/138" target="_blank" class="">https://github.com/p4lang/p4-s<wbr class="">pec/issues/138</a><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">* Header Unions (Continued) [15 minutes]</div>
<div class="">
<div class=""><br class="">
</div>
<div class="">* Table entries (Continued) [15 minutes]<br class="">
</div>
<div class=""><a href="https://github.com/p4lang/p4-spec/pull/127" target="_blank" class="">https://github.com/p4lang/p4-s<wbr class="">pec/pull/127</a><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">* Other business [10 minutes]<br class="">
</div>
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">Call-in details:</div>
<div class="">* By computer: <a href="https://cornell.zoom.us/j/959432658" target="_blank" class="">https://cornell.<span class="gmail-m_5201371115417210342gmail-m_5829737396568822684gmail-m_7817321662595553447gmail-m_672807707084920092gmail-m_3857355633148116987gmail-m_8246829709991880577gmail-il">zoom</span><wbr class="">.us/j/959432658</a></div>
<div class="">* By phone: <a href="tel:(646)%20558-8656" value="+16465588656" target="_blank" class="">+1 646 558 8656</a> (US Toll) or <a href="tel:(408)%20638-0968" value="+14086380968" target="_blank" class="">+1 408 638 0968</a> (US Toll). The Meeting ID
is 959 432 658. International numbers are available at <a href="https://cornell.zoom.us/zoomconference?m=p414IDyY2yeauZygZLycHH0Vnc0wYEFg" target="_blank" class="">https://cornell.<span class="gmail-m_5201371115417210342gmail-m_5829737396568822684gmail-m_7817321662595553447gmail-m_672807707084920092gmail-m_3857355633148116987gmail-m_8246829709991880577gmail-il">zoom</span>.us/zoo<wbr class="">mconference?m=p414IDyY2yeauZyg<wbr class="">ZLycHH0Vnc0wYEFg</a></div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br class="">
P4-design mailing list<br class="">
<a href="mailto:P4-design@lists.p4.org" class="">P4-design@lists.p4.org</a><br class="">
http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org<br class="">
<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>