-
Notifications
You must be signed in to change notification settings - Fork 448
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
Introduce the SKB metadata extern #4916
Conversation
@komaljai please take a look when you have some time |
60d30af
to
5e1e5f0
Compare
You can try to inherit EBPF class DeparserBodyTranslatorPSA in TC and make related changes in TC backend. |
Could you add example for skb metadata extern? |
I added the example in this commit 96707ea and rebased |
da95c99
to
e44e743
Compare
Done |
Head branch was pushed to by a user without write access
Tested with other examples we had and saw that this PR breaks one of our examples |
7a177fa
to
651dd08
Compare
d73b5ff
to
dbc19dc
Compare
@komaljai please take another look when you have some time |
Signed-off-by: Mouse <[email protected]>
Since we are not relying on recirculation to reset the skb protocol to the original value anymore, only recirculate if needed Signed-off-by: Mouse <[email protected]>
Signed-off-by: Mouse <[email protected]>
Signed-off-by: Mouse <[email protected]>
Signed-off-by: Mouse <[email protected]>
We are adding the SKB metadata extern to the tc backend's control blocks and deparser definitions
The main difference from the previous version is that we dropped the extern representation of the
skb(
tc_skb_metadata
), and made skb read/write operation into extern functions.So, for example, to set the skb protocol, the user should do the following:
And to retrive the skb protocol: