Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a standard way to precisely define behavior of P4 architectures #6

Closed
jafingerhut opened this issue Oct 2, 2022 · 1 comment
Labels
bigtask A job that would require a large amount of time, learning, and effort

Comments

@jafingerhut
Copy link
Owner

jafingerhut commented Oct 2, 2022

As of 2024-Sep-15, I (Andy Fingerhut) have given a presentation at a language design work group meeting either late in 2023 or early 2024 on some detailed proposals on one way that this could be done, in P4 with a small number of additional externs and extensions to the language. You can read more about that here:

There is no implementation of this anywhere that I know of, and I do not know of anyone actively working on developing one. I would expect the most useful places to create such an implementation would be:

  • in a software switch like BMv2 / simple_switch_grpc, to enable BMv2 to process packets according to P4 architectures defined in this new way.
  • in a tool like p4testgen
@jafingerhut jafingerhut added the bigtask A job that would require a large amount of time, learning, and effort label Sep 15, 2024
@jafingerhut
Copy link
Owner Author

Closing since all issues have been copied to this repo: https://github.com/p4lang/project-ideas/issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bigtask A job that would require a large amount of time, learning, and effort
Projects
None yet
Development

No branches or pull requests

1 participant