How a 64-bit process virtual address space is divided in Linux? The Next CEO of Stack OverflowLinux Kernel logical address space organisationhow is page size determined in virtual address space?Physical Address Extension - how do virtual addresses work?How can two identical virtual addresses point to different physical addresses?How does the CPU knows which physical address is mapped to which virtual address?how to get virtual address generated by a processHow can the Linux kernel address from 8 MB to 1 GB of virtual memory in x86 systemsDoes the isolation between virtual memory address spaces of different processes not apply to privileged process and to swap?Do the virtual address spaces of all the processes have the same content in their “Kernel” parts?Disabling virtual address space randomization for a linux kernel module
What does "Its cash flow is deeply negative" mean?
Plot of histogram similar to output from @risk
How to count occurrences of text in a file?
Why is information "lost" when it got into a black hole?
I believe this to be a fraud - hired, then asked to cash check and send cash as Bitcoin
Does falling count as part of my movement?
RigExpert AA-35 - Interpreting The Information
How to get from Geneva Airport to Metabief?
WOW air has ceased operation, can I get my tickets refunded?
Why do airplanes bank sharply to the right after air-to-air refueling?
Why isn't acceleration always zero whenever velocity is zero, such as the moment a ball bounces off a wall?
How many extra stops do monopods offer for tele photographs?
is it ok to reduce charging current for li ion 18650 battery?
How to invert MapIndexed on a ragged structure? How to construct a tree from rules?
Make solar eclipses exceedingly rare, but still have new moons
Is micro rebar a better way to reinforce concrete than rebar?
Won the lottery - how do I keep the money?
Fit as many overlapping generators as possible
Why does the flight controls check come before arming the autobrake on the A320?
What connection does MS Office have to Netscape Navigator?
Why the difference in type-inference over the as-pattern in two similar function definitions?
Is there a way to save my career from absolute disaster?
What did we know about the Kessel run before the prologues?
What was the first Unix version to run on a microcomputer?
How a 64-bit process virtual address space is divided in Linux?
The Next CEO of Stack OverflowLinux Kernel logical address space organisationhow is page size determined in virtual address space?Physical Address Extension - how do virtual addresses work?How can two identical virtual addresses point to different physical addresses?How does the CPU knows which physical address is mapped to which virtual address?how to get virtual address generated by a processHow can the Linux kernel address from 8 MB to 1 GB of virtual memory in x86 systemsDoes the isolation between virtual memory address spaces of different processes not apply to privileged process and to swap?Do the virtual address spaces of all the processes have the same content in their “Kernel” parts?Disabling virtual address space randomization for a linux kernel module
The following image shows how a 32-bit process virtual address space is divided:
But how a 64-bit process virtual address space is divided?
linux
asked 3 hours ago
ChristopherChristopher
1382
add a comment |
The following image shows how a 32-bit process virtual address space is divided:
But how a 64-bit process virtual address space is divided?
linux
asked 3 hours ago
ChristopherChristopher
1382
add a comment |
The following image shows how a 32-bit process virtual address space is divided:
But how a 64-bit process virtual address space is divided?
linux
asked 3 hours ago
ChristopherChristopher
1382
The following image shows how a 32-bit process virtual address space is divided:
But how a 64-bit process virtual address space is divided?
linux
linux
asked 3 hours ago
ChristopherChristopher
1382
asked 3 hours ago
ChristopherChristopher
1382
asked 3 hours ago
ChristopherChristopher
1382
asked 3 hours ago
ChristopherChristopher
1382
asked 3 hours ago
ChristopherChristopher
1382
1382
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The 64-bit x86 virtual memory map splits the address space into two: the lower section (with the top bit set to 0) is user-space, the upper section (with the top bit set to 1) is kernel-space. (Note that x86-64 defines “canonical” “lower half” and “higher half” addresses, with a number of bits effectively limited to 48 or 56; see Wikipedia for details.)
The complete map is documented in detail in the kernel; currently it looks like
===========================================================================================
Start addr | Offset | End addr | Size | VM area description
===========================================================================================
| | | |
0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory
__________________|____________|__________________|_________|______________________________
| | | |
0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | non-canonical
__________________|____________|__________________|_________|______________________________
| | | |
ffff800000000000 | -128 TB | ffffffffffffffff | 128 TB | kernel-space virtual memory
__________________|____________|__________________|_________|______________________________
with 48-bit virtual addresses.
Unlike the 32-bit case, the “64-bit” memory map is a direct reflection of hardware constraints.
answered 3 hours ago
Stephen KittStephen Kitt
179k24406484
To clarify: this limitation is imposed by the hardware. There is currently no 64-bit processor implementation that doesn't leave a huge hole of unusable addresses in the middle of the virtual address space. The amount of physical memory the CPUs are able to address is also way below 2 to the power of 64.
– Johan Myréen
2 hours ago
Thanks @Johan, I’ve tried to highlight this.
– Stephen Kitt
2 hours ago
add a comment |
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
);
);
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509607%2fhow-a-64-bit-process-virtual-address-space-is-divided-in-linux%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The 64-bit x86 virtual memory map splits the address space into two: the lower section (with the top bit set to 0) is user-space, the upper section (with the top bit set to 1) is kernel-space. (Note that x86-64 defines “canonical” “lower half” and “higher half” addresses, with a number of bits effectively limited to 48 or 56; see Wikipedia for details.)
The complete map is documented in detail in the kernel; currently it looks like
===========================================================================================
Start addr | Offset | End addr | Size | VM area description
===========================================================================================
| | | |
0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory
__________________|____________|__________________|_________|______________________________
| | | |
0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | non-canonical
__________________|____________|__________________|_________|______________________________
| | | |
ffff800000000000 | -128 TB | ffffffffffffffff | 128 TB | kernel-space virtual memory
__________________|____________|__________________|_________|______________________________
with 48-bit virtual addresses.
Unlike the 32-bit case, the “64-bit” memory map is a direct reflection of hardware constraints.
answered 3 hours ago
Stephen KittStephen Kitt
179k24406484
To clarify: this limitation is imposed by the hardware. There is currently no 64-bit processor implementation that doesn't leave a huge hole of unusable addresses in the middle of the virtual address space. The amount of physical memory the CPUs are able to address is also way below 2 to the power of 64.
– Johan Myréen
2 hours ago
Thanks @Johan, I’ve tried to highlight this.
– Stephen Kitt
2 hours ago
add a comment |
The 64-bit x86 virtual memory map splits the address space into two: the lower section (with the top bit set to 0) is user-space, the upper section (with the top bit set to 1) is kernel-space. (Note that x86-64 defines “canonical” “lower half” and “higher half” addresses, with a number of bits effectively limited to 48 or 56; see Wikipedia for details.)
The complete map is documented in detail in the kernel; currently it looks like
===========================================================================================
Start addr | Offset | End addr | Size | VM area description
===========================================================================================
| | | |
0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory
__________________|____________|__________________|_________|______________________________
| | | |
0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | non-canonical
__________________|____________|__________________|_________|______________________________
| | | |
ffff800000000000 | -128 TB | ffffffffffffffff | 128 TB | kernel-space virtual memory
__________________|____________|__________________|_________|______________________________
with 48-bit virtual addresses.
Unlike the 32-bit case, the “64-bit” memory map is a direct reflection of hardware constraints.
answered 3 hours ago
Stephen KittStephen Kitt
179k24406484
To clarify: this limitation is imposed by the hardware. There is currently no 64-bit processor implementation that doesn't leave a huge hole of unusable addresses in the middle of the virtual address space. The amount of physical memory the CPUs are able to address is also way below 2 to the power of 64.
– Johan Myréen
2 hours ago
Thanks @Johan, I’ve tried to highlight this.
– Stephen Kitt
2 hours ago
add a comment |
The 64-bit x86 virtual memory map splits the address space into two: the lower section (with the top bit set to 0) is user-space, the upper section (with the top bit set to 1) is kernel-space. (Note that x86-64 defines “canonical” “lower half” and “higher half” addresses, with a number of bits effectively limited to 48 or 56; see Wikipedia for details.)
The complete map is documented in detail in the kernel; currently it looks like
===========================================================================================
Start addr | Offset | End addr | Size | VM area description
===========================================================================================
| | | |
0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory
__________________|____________|__________________|_________|______________________________
| | | |
0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | non-canonical
__________________|____________|__________________|_________|______________________________
| | | |
ffff800000000000 | -128 TB | ffffffffffffffff | 128 TB | kernel-space virtual memory
__________________|____________|__________________|_________|______________________________
with 48-bit virtual addresses.
Unlike the 32-bit case, the “64-bit” memory map is a direct reflection of hardware constraints.
answered 3 hours ago
Stephen KittStephen Kitt
179k24406484
The 64-bit x86 virtual memory map splits the address space into two: the lower section (with the top bit set to 0) is user-space, the upper section (with the top bit set to 1) is kernel-space. (Note that x86-64 defines “canonical” “lower half” and “higher half” addresses, with a number of bits effectively limited to 48 or 56; see Wikipedia for details.)
The complete map is documented in detail in the kernel; currently it looks like
===========================================================================================
Start addr | Offset | End addr | Size | VM area description
===========================================================================================
| | | |
0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory
__________________|____________|__________________|_________|______________________________
| | | |
0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | non-canonical
__________________|____________|__________________|_________|______________________________
| | | |
ffff800000000000 | -128 TB | ffffffffffffffff | 128 TB | kernel-space virtual memory
__________________|____________|__________________|_________|______________________________
with 48-bit virtual addresses.
Unlike the 32-bit case, the “64-bit” memory map is a direct reflection of hardware constraints.
answered 3 hours ago
Stephen KittStephen Kitt
179k24406484
edited 2 hours ago
answered 3 hours ago
Stephen KittStephen Kitt
179k24406484
answered 3 hours ago
Stephen KittStephen Kitt
179k24406484
answered 3 hours ago
Stephen KittStephen Kitt
179k24406484
179k24406484
To clarify: this limitation is imposed by the hardware. There is currently no 64-bit processor implementation that doesn't leave a huge hole of unusable addresses in the middle of the virtual address space. The amount of physical memory the CPUs are able to address is also way below 2 to the power of 64.
– Johan Myréen
2 hours ago
Thanks @Johan, I’ve tried to highlight this.
– Stephen Kitt
2 hours ago
add a comment |
To clarify: this limitation is imposed by the hardware. There is currently no 64-bit processor implementation that doesn't leave a huge hole of unusable addresses in the middle of the virtual address space. The amount of physical memory the CPUs are able to address is also way below 2 to the power of 64.
– Johan Myréen
2 hours ago
Thanks @Johan, I’ve tried to highlight this.
– Stephen Kitt
2 hours ago
To clarify: this limitation is imposed by the hardware. There is currently no 64-bit processor implementation that doesn't leave a huge hole of unusable addresses in the middle of the virtual address space. The amount of physical memory the CPUs are able to address is also way below 2 to the power of 64.
– Johan Myréen
2 hours ago
To clarify: this limitation is imposed by the hardware. There is currently no 64-bit processor implementation that doesn't leave a huge hole of unusable addresses in the middle of the virtual address space. The amount of physical memory the CPUs are able to address is also way below 2 to the power of 64.
– Johan Myréen
2 hours ago
Thanks @Johan, I’ve tried to highlight this.
– Stephen Kitt
2 hours ago
Thanks @Johan, I’ve tried to highlight this.
– Stephen Kitt
2 hours ago
add a comment |
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.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509607%2fhow-a-64-bit-process-virtual-address-space-is-divided-in-linux%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
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
