What prevents my RT thread from working?












1















I have some data acquisition application running under Linux 2.6.37 on DM8148 with TI Linux. I have two threads:





  • thread named IDE, scheduled as SCHED_RR, prio 114 (75), which collects data from HW FIFO arriving at 200KiB/s into 30MiB ring buffer each 2ms:



    while(1) {
    sleep(ms);
    while(DataInFIFO) {
    CollectToRingBuffer();
    SignalToWriter(); }
    }



  • thread WriterIDE, scheduled as SCHED_RR, prio 113 (74), writing this ring buffer in to the USB disk-on-key.



    while(1) {
    WaitForSignal();
    writeToFileOnDOK();
    }



I know from measures of "write()" function that sometimes this USB writing may "hang" for some 1.5 and even 2 seconds, trying to write to the DOK. But I was sure that as I gave the collector task 30MiB, which is enough for 150s, everything will be OK.



No! It is not!

I put the time measuring code. And what I see is, that when writer hangs for a long time (f.e.1342ms), then entering the collector thread time also is very large (306ms). This causes HW FIFO overflow and data inconsistency.



I checked the spread of threads priority in the system (ps command) - nothing is real-time, except me. All system tasks are scheduled as OTHER (TS in ps output), even kernel USB threads. Only IRQ tasks are FF, but even them are of lower priority.



I don't know where to go from here...:-(

Please, help!










share|improve this question



























    1















    I have some data acquisition application running under Linux 2.6.37 on DM8148 with TI Linux. I have two threads:





    • thread named IDE, scheduled as SCHED_RR, prio 114 (75), which collects data from HW FIFO arriving at 200KiB/s into 30MiB ring buffer each 2ms:



      while(1) {
      sleep(ms);
      while(DataInFIFO) {
      CollectToRingBuffer();
      SignalToWriter(); }
      }



    • thread WriterIDE, scheduled as SCHED_RR, prio 113 (74), writing this ring buffer in to the USB disk-on-key.



      while(1) {
      WaitForSignal();
      writeToFileOnDOK();
      }



    I know from measures of "write()" function that sometimes this USB writing may "hang" for some 1.5 and even 2 seconds, trying to write to the DOK. But I was sure that as I gave the collector task 30MiB, which is enough for 150s, everything will be OK.



    No! It is not!

    I put the time measuring code. And what I see is, that when writer hangs for a long time (f.e.1342ms), then entering the collector thread time also is very large (306ms). This causes HW FIFO overflow and data inconsistency.



    I checked the spread of threads priority in the system (ps command) - nothing is real-time, except me. All system tasks are scheduled as OTHER (TS in ps output), even kernel USB threads. Only IRQ tasks are FF, but even them are of lower priority.



    I don't know where to go from here...:-(

    Please, help!










    share|improve this question

























      1












      1








      1








      I have some data acquisition application running under Linux 2.6.37 on DM8148 with TI Linux. I have two threads:





      • thread named IDE, scheduled as SCHED_RR, prio 114 (75), which collects data from HW FIFO arriving at 200KiB/s into 30MiB ring buffer each 2ms:



        while(1) {
        sleep(ms);
        while(DataInFIFO) {
        CollectToRingBuffer();
        SignalToWriter(); }
        }



      • thread WriterIDE, scheduled as SCHED_RR, prio 113 (74), writing this ring buffer in to the USB disk-on-key.



        while(1) {
        WaitForSignal();
        writeToFileOnDOK();
        }



      I know from measures of "write()" function that sometimes this USB writing may "hang" for some 1.5 and even 2 seconds, trying to write to the DOK. But I was sure that as I gave the collector task 30MiB, which is enough for 150s, everything will be OK.



      No! It is not!

      I put the time measuring code. And what I see is, that when writer hangs for a long time (f.e.1342ms), then entering the collector thread time also is very large (306ms). This causes HW FIFO overflow and data inconsistency.



      I checked the spread of threads priority in the system (ps command) - nothing is real-time, except me. All system tasks are scheduled as OTHER (TS in ps output), even kernel USB threads. Only IRQ tasks are FF, but even them are of lower priority.



      I don't know where to go from here...:-(

      Please, help!










      share|improve this question














      I have some data acquisition application running under Linux 2.6.37 on DM8148 with TI Linux. I have two threads:





      • thread named IDE, scheduled as SCHED_RR, prio 114 (75), which collects data from HW FIFO arriving at 200KiB/s into 30MiB ring buffer each 2ms:



        while(1) {
        sleep(ms);
        while(DataInFIFO) {
        CollectToRingBuffer();
        SignalToWriter(); }
        }



      • thread WriterIDE, scheduled as SCHED_RR, prio 113 (74), writing this ring buffer in to the USB disk-on-key.



        while(1) {
        WaitForSignal();
        writeToFileOnDOK();
        }



      I know from measures of "write()" function that sometimes this USB writing may "hang" for some 1.5 and even 2 seconds, trying to write to the DOK. But I was sure that as I gave the collector task 30MiB, which is enough for 150s, everything will be OK.



      No! It is not!

      I put the time measuring code. And what I see is, that when writer hangs for a long time (f.e.1342ms), then entering the collector thread time also is very large (306ms). This causes HW FIFO overflow and data inconsistency.



      I checked the spread of threads priority in the system (ps command) - nothing is real-time, except me. All system tasks are scheduled as OTHER (TS in ps output), even kernel USB threads. Only IRQ tasks are FF, but even them are of lower priority.



      I don't know where to go from here...:-(

      Please, help!







      linux-kernel io priority real-time multi-threaded






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 27 at 15:19









      leonpleonp

      1061




      1061






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fsuperuser.com%2fquestions%2f1398952%2fwhat-prevents-my-rt-thread-from-working%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 Super User!


          • 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%2fsuperuser.com%2fquestions%2f1398952%2fwhat-prevents-my-rt-thread-from-working%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

          Plaza Victoria

          Puebla de Zaragoza

          Musa