iostat: what is exactly the concept of merge

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











up vote
1
down vote

favorite












From iostat man pages:



rrqm/s
The number of read requests merged per second that were queued to the device.

wrqm/s
The number of write requests merged per second that were queued to the device.

r/s
The number (after merges) of read requests completed per second for the device.

w/s
The number (after merges) of write requests completed per second for the device.


Can anyone elaborate on the merge concept since the documentation does not provide any further details?










share|improve this question



























    up vote
    1
    down vote

    favorite












    From iostat man pages:



    rrqm/s
    The number of read requests merged per second that were queued to the device.

    wrqm/s
    The number of write requests merged per second that were queued to the device.

    r/s
    The number (after merges) of read requests completed per second for the device.

    w/s
    The number (after merges) of write requests completed per second for the device.


    Can anyone elaborate on the merge concept since the documentation does not provide any further details?










    share|improve this question

























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      From iostat man pages:



      rrqm/s
      The number of read requests merged per second that were queued to the device.

      wrqm/s
      The number of write requests merged per second that were queued to the device.

      r/s
      The number (after merges) of read requests completed per second for the device.

      w/s
      The number (after merges) of write requests completed per second for the device.


      Can anyone elaborate on the merge concept since the documentation does not provide any further details?










      share|improve this question















      From iostat man pages:



      rrqm/s
      The number of read requests merged per second that were queued to the device.

      wrqm/s
      The number of write requests merged per second that were queued to the device.

      r/s
      The number (after merges) of read requests completed per second for the device.

      w/s
      The number (after merges) of write requests completed per second for the device.


      Can anyone elaborate on the merge concept since the documentation does not provide any further details?







      io iostat






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 15 at 9:43









      Rui F Ribeiro

      36.6k1271116




      36.6k1271116










      asked Aug 15 at 9:03









      pkaramol

      338112




      338112




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          A merge happens when two i/o requests can be collapsed into one single longer-length request. For example, a write to block 1234 followed by a write to block 1235 can be merged into a single i/o request for block 1234 of length 2 blocks. As this sort of situation can be fairly common it is worth putting the effort in the kernel to do the merge, freeing up an i/o request structture, and reducing interrupt overhead.



          If you are interested in more detailed statistics on this aspect of i/o see the pdf btt user guide which is part of blktrace.






          share|improve this answer






















            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',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            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%2f462704%2fiostat-what-is-exactly-the-concept-of-merge%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote



            accepted










            A merge happens when two i/o requests can be collapsed into one single longer-length request. For example, a write to block 1234 followed by a write to block 1235 can be merged into a single i/o request for block 1234 of length 2 blocks. As this sort of situation can be fairly common it is worth putting the effort in the kernel to do the merge, freeing up an i/o request structture, and reducing interrupt overhead.



            If you are interested in more detailed statistics on this aspect of i/o see the pdf btt user guide which is part of blktrace.






            share|improve this answer


























              up vote
              2
              down vote



              accepted










              A merge happens when two i/o requests can be collapsed into one single longer-length request. For example, a write to block 1234 followed by a write to block 1235 can be merged into a single i/o request for block 1234 of length 2 blocks. As this sort of situation can be fairly common it is worth putting the effort in the kernel to do the merge, freeing up an i/o request structture, and reducing interrupt overhead.



              If you are interested in more detailed statistics on this aspect of i/o see the pdf btt user guide which is part of blktrace.






              share|improve this answer
























                up vote
                2
                down vote



                accepted







                up vote
                2
                down vote



                accepted






                A merge happens when two i/o requests can be collapsed into one single longer-length request. For example, a write to block 1234 followed by a write to block 1235 can be merged into a single i/o request for block 1234 of length 2 blocks. As this sort of situation can be fairly common it is worth putting the effort in the kernel to do the merge, freeing up an i/o request structture, and reducing interrupt overhead.



                If you are interested in more detailed statistics on this aspect of i/o see the pdf btt user guide which is part of blktrace.






                share|improve this answer














                A merge happens when two i/o requests can be collapsed into one single longer-length request. For example, a write to block 1234 followed by a write to block 1235 can be merged into a single i/o request for block 1234 of length 2 blocks. As this sort of situation can be fairly common it is worth putting the effort in the kernel to do the merge, freeing up an i/o request structture, and reducing interrupt overhead.



                If you are interested in more detailed statistics on this aspect of i/o see the pdf btt user guide which is part of blktrace.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Aug 15 at 12:16

























                answered Aug 15 at 12:10









                meuh

                30k11752




                30k11752



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f462704%2fiostat-what-is-exactly-the-concept-of-merge%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

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

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?