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

OVS: Extract flow information #439

Open
amorenoz opened this issue Oct 30, 2024 · 2 comments
Open

OVS: Extract flow information #439

amorenoz opened this issue Oct 30, 2024 · 2 comments
Milestone

Comments

@amorenoz
Copy link
Contributor

Currently, the OVS module hooks into the ovs_do_execute_action tracepoint and extracts some basic action information.

However, in order to get a more complete picture of what OVS is doing with the packet, it would be nice to get some datapath flow information. Even if we don't implement a full key parsing library, extracting the UFID will be helpful as it can then be enriched by OVS.

Unfortunately, the UFID is not easily available in a tracepoint so some kprobe/kretprobe workaround will be needed (until OVS developers add a good tracepoint, wink wink).

@atenart
Copy link
Contributor

atenart commented Oct 30, 2024

Unfortunately, the UFID is not easily available in a tracepoint so some kprobe/kretprobe workaround will be needed (until OVS developers add a good tracepoint, wink wink).

FYI noinline_for_tracing is currently under discussion, which is a good starting point before adding a tracepoint.

@vlrpl
Copy link
Contributor

vlrpl commented Oct 30, 2024

Unfortunately, the UFID is not easily available in a tracepoint so some kprobe/kretprobe workaround will be needed (until OVS developers add a good tracepoint, wink wink).

FYI noinline_for_tracing is currently under discussion, which is a good starting point before adding a tracepoint.

Interesting. Fortunately, the symbol can be probed, it should just be inconvenient to retrieve the data.
This is the case where fexit shines (args access).

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

No branches or pull requests

3 participants