What is the value for the cgroup's limit_in_bytes if the memory is not restricted/unlimited?

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











up vote
2
down vote

favorite












Printing the value of an unlimited docker container I get the value 9223372036854771712 which is 0x7FFFFFFFFFFFF000 (this is the same value of the XUbuntu Host machine). I couldn't find a reference that this is the Docker or Linux default value indicating an unlimited memory resource.



Where does this value come from?
Is it different between Container Virtualizations or Linux Distributions/Bitnesses?







share|improve this question


























    up vote
    2
    down vote

    favorite












    Printing the value of an unlimited docker container I get the value 9223372036854771712 which is 0x7FFFFFFFFFFFF000 (this is the same value of the XUbuntu Host machine). I couldn't find a reference that this is the Docker or Linux default value indicating an unlimited memory resource.



    Where does this value come from?
    Is it different between Container Virtualizations or Linux Distributions/Bitnesses?







    share|improve this question
























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      Printing the value of an unlimited docker container I get the value 9223372036854771712 which is 0x7FFFFFFFFFFFF000 (this is the same value of the XUbuntu Host machine). I couldn't find a reference that this is the Docker or Linux default value indicating an unlimited memory resource.



      Where does this value come from?
      Is it different between Container Virtualizations or Linux Distributions/Bitnesses?







      share|improve this question














      Printing the value of an unlimited docker container I get the value 9223372036854771712 which is 0x7FFFFFFFFFFFF000 (this is the same value of the XUbuntu Host machine). I couldn't find a reference that this is the Docker or Linux default value indicating an unlimited memory resource.



      Where does this value come from?
      Is it different between Container Virtualizations or Linux Distributions/Bitnesses?









      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 31 at 11:26

























      asked Jan 31 at 11:10









      Christian Ammer

      11815




      11815




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          The value comes from the cgroup setup in the memory management layer; by default, it’s set to PAGE_COUNTER_MAX, which is LONG_MAX / PAGE_SIZE on 64-bit platforms, and multiplied by PAGE_SIZE again when read.



          This confirms ilkkachu’s explanation: the value is the maximum 64-bit signed integer, rounded to the nearest page (by dropping the last bits).






          share|improve this answer



























            up vote
            2
            down vote













            That's the highest positive signed 64-bit integer (263-1), rounded down to multiples of 4096 (212), the most common page size on x86 systems. It would seem difficult to get anything higher while avoiding possible confusion between signed and unsigned, so it seems at least a reasonable approximation for infinity.



            That said, I don't know for sure, this is just a guess.






            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%2f420906%2fwhat-is-the-value-for-the-cgroups-limit-in-bytes-if-the-memory-is-not-restricte%23new-answer', 'question_page');

              );

              Post as a guest






























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              2
              down vote



              accepted










              The value comes from the cgroup setup in the memory management layer; by default, it’s set to PAGE_COUNTER_MAX, which is LONG_MAX / PAGE_SIZE on 64-bit platforms, and multiplied by PAGE_SIZE again when read.



              This confirms ilkkachu’s explanation: the value is the maximum 64-bit signed integer, rounded to the nearest page (by dropping the last bits).






              share|improve this answer
























                up vote
                2
                down vote



                accepted










                The value comes from the cgroup setup in the memory management layer; by default, it’s set to PAGE_COUNTER_MAX, which is LONG_MAX / PAGE_SIZE on 64-bit platforms, and multiplied by PAGE_SIZE again when read.



                This confirms ilkkachu’s explanation: the value is the maximum 64-bit signed integer, rounded to the nearest page (by dropping the last bits).






                share|improve this answer






















                  up vote
                  2
                  down vote



                  accepted







                  up vote
                  2
                  down vote



                  accepted






                  The value comes from the cgroup setup in the memory management layer; by default, it’s set to PAGE_COUNTER_MAX, which is LONG_MAX / PAGE_SIZE on 64-bit platforms, and multiplied by PAGE_SIZE again when read.



                  This confirms ilkkachu’s explanation: the value is the maximum 64-bit signed integer, rounded to the nearest page (by dropping the last bits).






                  share|improve this answer












                  The value comes from the cgroup setup in the memory management layer; by default, it’s set to PAGE_COUNTER_MAX, which is LONG_MAX / PAGE_SIZE on 64-bit platforms, and multiplied by PAGE_SIZE again when read.



                  This confirms ilkkachu’s explanation: the value is the maximum 64-bit signed integer, rounded to the nearest page (by dropping the last bits).







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Feb 1 at 11:10









                  Stephen Kitt

                  142k22308370




                  142k22308370






















                      up vote
                      2
                      down vote













                      That's the highest positive signed 64-bit integer (263-1), rounded down to multiples of 4096 (212), the most common page size on x86 systems. It would seem difficult to get anything higher while avoiding possible confusion between signed and unsigned, so it seems at least a reasonable approximation for infinity.



                      That said, I don't know for sure, this is just a guess.






                      share|improve this answer
























                        up vote
                        2
                        down vote













                        That's the highest positive signed 64-bit integer (263-1), rounded down to multiples of 4096 (212), the most common page size on x86 systems. It would seem difficult to get anything higher while avoiding possible confusion between signed and unsigned, so it seems at least a reasonable approximation for infinity.



                        That said, I don't know for sure, this is just a guess.






                        share|improve this answer






















                          up vote
                          2
                          down vote










                          up vote
                          2
                          down vote









                          That's the highest positive signed 64-bit integer (263-1), rounded down to multiples of 4096 (212), the most common page size on x86 systems. It would seem difficult to get anything higher while avoiding possible confusion between signed and unsigned, so it seems at least a reasonable approximation for infinity.



                          That said, I don't know for sure, this is just a guess.






                          share|improve this answer












                          That's the highest positive signed 64-bit integer (263-1), rounded down to multiples of 4096 (212), the most common page size on x86 systems. It would seem difficult to get anything higher while avoiding possible confusion between signed and unsigned, so it seems at least a reasonable approximation for infinity.



                          That said, I don't know for sure, this is just a guess.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jan 31 at 11:21









                          ilkkachu

                          49.8k674137




                          49.8k674137






















                               

                              draft saved


                              draft discarded


























                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f420906%2fwhat-is-the-value-for-the-cgroups-limit-in-bytes-if-the-memory-is-not-restricte%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?