Skip to content

Bypass mode for ebpf, first steps#147

Merged
haesbaert merged 1 commit into
mainfrom
bypass
Apr 4, 2025
Merged

Bypass mode for ebpf, first steps#147
haesbaert merged 1 commit into
mainfrom
bypass

Conversation

@haesbaert
Copy link
Copy Markdown
Collaborator

@haesbaert haesbaert commented Apr 3, 2025

This implements a bypass mode that only works on ebpf.
In this mode, a quark_event is always QUARK_EV_BYPASS and the only member filled
is bypass.

The purpose of this is to make it feasible to use quark as an ebpf loader only,
letting the user tap directly into the ebpf ring.

There's no pre-processing, no caching, no allocations and so on. Bypass is
really just a direct path to access bpf's ringbuffer.

This implements a bypass mode that only works on ebpf.
In this mode, a quark_event is always QUARK_EV_BYPASS and the only member filled
is `bypass`.

The purpose of this is to make it feasible to use quark as an ebpf loader only,
letting the user tap directly into the ebpf ring.

There's no pre-processing, no caching, no allocations and so on. Bypass is
really just a direct path to access bpf's ringbuffer.
@haesbaert haesbaert changed the title WIP: bypass mode for ebpf Bypass mode for ebpf, first steps Apr 3, 2025
@haesbaert haesbaert marked this pull request as ready for review April 3, 2025 22:56
@haesbaert haesbaert requested a review from a team as a code owner April 3, 2025 22:56
@haesbaert haesbaert merged commit 8cc0265 into main Apr 4, 2025
2 checks passed
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