Listen to specific event types via process netlink connector

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












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?










share|improve this question


























    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?










    share|improve this question
























      0












      0








      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?










      share|improve this question














      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?







      socket unix-sockets






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 10 at 9:58









      divyanshmdivyanshm

      768




      768




















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493650%2flisten-to-specific-event-types-via-process-netlink-connector%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493650%2flisten-to-specific-event-types-via-process-netlink-connector%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown






          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay