No, it's not
learn about operating systems userspace and then kernelspace and then exposes between them and different kind of lowmem highmem virtual physical memory access stuffs and managements then you can fresh your question in the first place. if you mean your own userspace process's vas yes through implementing a vas memory manager or proper manual management, basicaly reserve all of your needed memory and manage it yourself, or place your stuffs in proper structures and disable compiler's memory rearrangement features. if you mean direct memory access in userspace yes through some protected envs like vfio or in kernel space implementing a device driver and your own mmap in it, reserve an available cm range and manage it for your userspace program, etc etc etc but there is always some isolations and restrictions based on when and where you do it for sake of saving integrity of important stuffs, saving fast CMA regions, etc and you can't magicaly jump on all reserved addresses. but generaly yes everything is possible but has its costs which sometimes does not deserve it. but before anything learn to research, no human have everything in mind and nobody will write book in telegram for you and whatever anybody say will be clipped or unclear. whenever anybody try to explain huge topics (s)he probably makes joke of it, so if you don't want waste your life with making joke of people, take control spend time and research, then ask question about very detailed little parts of your real problems which also helps people to learn from it
@John1828 look this article, "An introduction to virtual memory", looks very interesting https://news.ycombinator.com/item?id=23096747
Обсуждают сегодня