P4: Programming Protocol-Independent Packet Processors
P4 is a high-level language for programming protocol-inde-pendent packet processors. P4 works in conjunction with SDN control protocols like OpenFlow. In its current form, OpenFlow explicitly speci es protocol headers on which it operates. This set has grown from 12 to 41 elds in a few years, increasing the complexity of the speci cation while
Download P4: Programming Protocol-Independent Packet Processors
Information
Domain:
Source:
Link to this page:
Related documents
Thinking in Java, 2nd Edition
vergil.chemistry.gatech.eduSoftware Engineer, Kestral Computing Thank you for Thinking in Java. It’s time someone went beyond mere language description to a thoughtful, penetrating analytic tutorial that doesn’t kowtow to The Manufacturers. I’ve read almost all the others— only yours and Patrick Winston’s have found a …
Introduction to the Java Programming Language
www.cs.drexel.eduSoftware Design (Java Tutorial) © SERG Software Design Introduction to the Java Programming Language Material drawn from [JDK99,Sun96,Mitchell99,Mancoridis00]
Java Code Conventions - Oracle
www.oracle.comThis document reflects the Java language coding standards presented in the Java Language Specification, from Sun Microsystems. Major contributions are from Peter King, Patrick Naughton, Mike DeMoney, Jonni Kanerva, Kathy Walrath, and Scott Hommel. For questions concerning adaptation, modification, or redistribution of this document, please
Assembly Language Tutorial
www.tutorialspoint.comAssembly Programming Tutorial Assembly language is a low-level programming language for a computer, or other programmable device specific to a particular computer architecture in contrast to most high-level programming languages, …
An Introduction to Software Architecture
sunnyday.mit.edurequired from the programming language, of course, but the abstract data type paradigm allowed some parts of systems to be developed from a vocabulary of data types rather than from a vocabulary of programming-language constructs. 2.3. Software Architecture Just as good programmers recognized useful data structures in the late 1960s,