/sys/fs/bpf hierarchy reflecting sensors/programs/etc. #408
Assignees
Comments
kkourt
added a commit
that referenced
this issue
Sep 15, 2022
This is meant to be used by sensors to create paths for their objects under /sys/fs/bpf. Ideally, we would want a directory hierarchy under each sensor, as described in #408. This is currently not easy to do, however. Instead, use a function that adds "-" instead of "/", leading to a flat hiearachy that has unique names. This function can be changed to filepath.Join once everything is in place. The purpose of the function is to document the above intention. Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
kkourt
added a commit
that referenced
this issue
Sep 15, 2022
This is meant to be used by sensors to create paths for their objects under /sys/fs/bpf. Ideally, we would want a directory hierarchy under each sensor, as described in #408. This is currently not easy to do, however. Instead, use a function that adds "-" instead of "/", leading to a flat hierarchy that has unique names. This function can be changed to filepath.Join once everything is in place. The purpose of the function is to document the above intention. Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
kkourt
added a commit
that referenced
this issue
Sep 16, 2022
This is meant to be used by sensors to create paths for their objects under /sys/fs/bpf. Ideally, we would want a directory hierarchy under each sensor, as described in #408. This is currently not easy to do, however. Instead, use a function that adds "-" instead of "/", leading to a flat hierarchy that has unique names. This function can be changed to filepath.Join once everything is in place. The purpose of the function is to document the above intention. Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
kkourt
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: