User avatar
Xerz πŸ’— @xerz@masfloss.net
3d
what sexos.dev
8
0
2
0
3d
@xerz The idea of a single shared address space (but protected by some novel Intel hardware feature I had no idea about) is original, that's for sure, but...

...SLOP!!!
blob_uooo
1
1
2
0
User avatar
[GRLC] kasane tito @novenary@akko.wtf
3d
@cinnamon @xerz is unified address space particularly novel? with 64 bit and ASLR it just makes sense for the most part
the only major objection is when something uses virtual memory in a funny way (e.g. emulators that replicate the system's memory layout for simplicity) but that's kind of at odds with ASLR anyway
1
0
1
0
User avatar
illy [Shrimple-mode] protomoji_orange_flag_lesbian @illyBytes@shrimp.imsofucking.gay
1d
@novenary @cinnamon @xerz virtual address space helps with having a function with a static variable that doesnt get cleared between function calls iirc
:blobcatthinkingeyes@mk.absturztau.be:1
2
0
0
1
User avatar
[GRLC] kasane tito @novenary@akko.wtf
1d
@illyBytes @cinnamon @xerz single address space is not mutually exclusive with virtual memory
1
0
1
0
User avatar
illy [Shrimple-mode] protomoji_orange_flag_lesbian @illyBytes@shrimp.imsofucking.gay
1d
@novenary @cinnamon @xerz oh wait maybe i misunderstood?
:celeste_hearts_catgender@mk.absturztau.be:1
1
0
0
1
User avatar
[GRLC] kasane tito @novenary@akko.wtf
1d
@illyBytes @cinnamon @xerz single address space in this case means you have a global page table shared between all processes, as opposed to one per process
this means that all memory is mapped at all times, and shared memory has the same address for everyone who has access to it
this simplifies a number of things and it also helps performance, but it requires a different mechanism for memory protection which x86 simply doesn't have

en.wikipedia.org/wiki/Single_address_space_operating_system
2
1
1
0
User avatar
illy [Shrimple-mode] protomoji_orange_flag_lesbian @illyBytes@shrimp.imsofucking.gay
1d
@novenary @cinnamon @xerz oooooh alright
0
0
0
0