0

I'm authoring a user app that would listen to process events via the process netlink connector.

While listening on the socket, my process spends a lot of time doing busy work because of lots of PROC_EVENT_COMM events being fired by the kernel.

I saw the source code for forkstat but that seems to be having the same problem. Is it not possible to only filter the events that we need on the receiving end of the socket - and save the busy work being done by the user process?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.