What is the value for the cgroup's limit_in_bytes if the memory is not restricted/unlimited?
Clash 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?
memory docker cgroups
add a comment |Â
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?
memory docker cgroups
add a comment |Â
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?
memory docker cgroups
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?
memory docker cgroups
edited Jan 31 at 11:26
asked Jan 31 at 11:10
Christian Ammer
11815
11815
add a comment |Â
add a comment |Â
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).
add a comment |Â
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.
add a comment |Â
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).
add a comment |Â
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).
add a comment |Â
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).
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).
answered Feb 1 at 11:10
Stephen Kitt
142k22308370
142k22308370
add a comment |Â
add a comment |Â
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.
add a comment |Â
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.
add a comment |Â
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.
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.
answered Jan 31 at 11:21
ilkkachu
49.8k674137
49.8k674137
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password