You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending events from eBPF programs to userspace, we always allocate the max length of bytes the given field supports. For example, in file-system-monitor, we send filenames of NAME_MAX length (1024) even when it's much shorter. Moreover, this leads us to being excessively conservative with the maximum field lengths.
We should design a data structure/protocol which allows to send only the data actually needed.
The text was updated successfully, but these errors were encountered:
When sending events from eBPF programs to userspace, we always allocate the max length of bytes the given field supports. For example, in file-system-monitor, we send filenames of
NAME_MAX
length (1024) even when it's much shorter. Moreover, this leads us to being excessively conservative with the maximum field lengths.We should design a data structure/protocol which allows to send only the data actually needed.
The text was updated successfully, but these errors were encountered: