i need resources on memory management in microkernels, anyone have pointers
i made this post and it's a stupid joke and it wasn't even intentional i swear!!!
@jk fuckkkkkk
@er1n (i love the choice of example in this:
"Thus, it is well settled that persons engaged in any undertakings outside what is common for a normal person, such as running a nuclear power plant,")
@er1n it's a good joke, though. i lol'd
maple classic™ 
@er1n if it helps any i never parsed it as a joke until you mentioned it because i've never used memory pointers for anything
@er1n
BUT IT WAS A GOOD JOKE ERIN D:
@er1n *slaps forehead*
@er1n don't do any, it is microer
@er1n 0x00000000
@er1n boo. Take your pity chuckle and go.
@aaronscientiae i DIDN'T MEAN TO MAKE A JOKE I SWEAR
@er1n oh. Sorry. then i guess check out code of what people have done before theres gotta be some good examples in os courses textbooks or look up some open courseware texts?
@er1n also probably buried in the descriptions of and changes recently to linux regarding meltdown and spectre might be useful.
@er1n To run the joke into the ground...
0x00158000000000000A8BC022E900023F with tag bits set.
(And yes, that's a real pointer. That I just copied off of a running system.)
@samis @er1n AFAIK that's a bit... complicated, it has a lot of microkernel concepts even if enough is implemented down in SLIC for it to not /really/ be a microkernel. Message passing all the things is absolutely part of it.
(Kinda like how PowerPC is arguably not really RISC, but it uses a lot of RISC concepts.)
And... yes, it points to something important. (The address is also going to be unique to a given OS install.)
@bhtooefr points for effort
@er1n did you get a good answer? I like the seL4 philosophy on memory management: there's a way for one task to transfer ownership of some physical pages to another task; paging is handled in userspace somehow (?); and when a task wants some service from either the kernel or some userspace server where completing the task requires some extra memory, then the client transfers ownership of enough pages over out of its own allocation, so trusted code never runs out of memory.
@er1n gods I almost can't tell if this is just a pun or you actually want resources
*claps*
@er1n here's some stuff below, but in general I think all microkernels do is allocate anonymous chunks of memory to applications running on them that request RAM, (where "application" is often the OS services and similar), and then its those processes jobs to do more management on it.
https://l4re.org/doc/l4re_concepts_ds_rm.html
https://www.gnu.org/software/hurd/open_issues/gnumach_memory_management.html
http://wiki.minix3.org/doku.php?id=developersguide:vminternals&s[]=memory&s[]=management
https://os.inf.tu-dresden.de/papers_ps/kauer-diplom-talk.pdf
@mmu_man yeah, it's a pretty good resource but it mostly focuses on small monolithic kernels :(
i ended up finding what i was looking for, anyway, though! thanks for replying seriously though, instead of pointing out that i accidentally made a joke :D
@er1n oh, just got it :D
OH MY GOD I JUST REALIZED THIS IS A FUKCING JOKE AND I HATE IT