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

Fixed ebpf_packetOffsetInBits field in parser and control_block C file #4233

Merged
merged 8 commits into from
Nov 14, 2023

Conversation

komaljai
Copy link
Contributor

@komaljai komaljai commented Nov 9, 2023

  1. In the control block C file, the code is checking to see if the parsed packet is smaller than the packet that will be generated by the deparser. The problem is that ebpf_packetOffsetInBits is set by the parser C file, but is not being passed on to the control block C file. The solution is to make ebpf_packetOffsetInBits part of the eBPF map struct in header file, which is included in both parser and control block C file
  2. Change permisson for default action.
  3. Convert header fields to host endian in parser.c file

Copy link
Contributor

@usha1830 usha1830 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@komaljai
Copy link
Contributor Author

I see the fedora and ptf tests are failing, and it is not related to this PR, Are others also facing the same issue?

@usha1830 usha1830 merged commit aa9f33f into p4lang:main Nov 14, 2023
13 checks passed
fruffy pushed a commit that referenced this pull request Nov 21, 2023
#4233)

* Fixed ebpf_packetOffsetInBits field in parser and control_block C file
* Move pna.h from tc runtime to ebpf runtime
* Change Permisson for Default Action.
* Reverse endianess conversion - Convert header fields to host endian
* Reverse movement of pna.h file from ebpf/runtime to tc/runtime
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants