From 3bf27c93ac4de57623809b71517116d51465f0e1 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sat, 17 Mar 2012 12:31:07 +0100 Subject: IRC bits. --- microkernel/mach/memory_object/discussion.mdwn | 13 +++-- microkernel/mach/pmap.mdwn | 74 ++++++++++++++++++++++++++ 2 files changed, 84 insertions(+), 3 deletions(-) create mode 100644 microkernel/mach/pmap.mdwn (limited to 'microkernel/mach') diff --git a/microkernel/mach/memory_object/discussion.mdwn b/microkernel/mach/memory_object/discussion.mdwn index a2a1514b..907f859a 100644 --- a/microkernel/mach/memory_object/discussion.mdwn +++ b/microkernel/mach/memory_object/discussion.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2011, 2012 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -10,7 +10,10 @@ License|/fdl]]."]]"""]] [[!tag open_issue_documentation open_issue_gnumach]] -IRC, freenode, #hurd, 2011-08-05: +[[!toc]] + + +# IRC, freenode, #hurd, 2011-08-05 < neal> braunr: For instance, memory objects are great as they allow you to specify the mapping policy in user space. @@ -23,7 +26,8 @@ IRC, freenode, #hurd, 2011-08-05: < braunr> the kernel eviction policy :) < neal> that's an implementation detail -IRC, freenode, #hurd, 2011-09-05: + +# IRC, freenode, #hurd, 2011-09-05 mach isn't a true modern microkernel, it handles a lot of resources, such as high level virtual memory and cpu time @@ -65,3 +69,6 @@ IRC, freenode, #hurd, 2011-09-05: pages are going to be flushed by themselves [[open_issues/resource_management_problems]]. + + +# [[open_issues/memory_object_model_vs_block-level_cache]] diff --git a/microkernel/mach/pmap.mdwn b/microkernel/mach/pmap.mdwn new file mode 100644 index 00000000..6910bfd3 --- /dev/null +++ b/microkernel/mach/pmap.mdwn @@ -0,0 +1,74 @@ +[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!tag open_issue_documentation open_issue_gnumach]] + + +# IRC, freenode, #hurd, 2012-02-01 + + on Hurd what is the difference between kernel memory object and + pmap module ?? + pmap is heap/libraries table for each thread while kernel memory + object refers to arbitary blobs of data ?? + sekon: pmap is the low level memory mapping module + i.e. it programs the mmu + and these aren't hurd-specific, they are mach modules + braunr: so kernel memonry objects consists of a bunch of pmaps ?? + sekon: memory objects can be various things, be specific please + (they're certainly not a bunch of pmaps though, no) + there is one pmap per vm_map, and there is one vm_map per task + and there is no need for double question marks, is ther ?? + lol then is kernel memory object , please excuse the metaphor + something like a base class for pmap + i don't know what a "kernel memory object" is, be specific please, + again + braunr: + http://courses.cs.vt.edu/~cs5204/fall05-gback/presentations/MachOS_Rajesh.ppt + goto page titled External Memory Management (EMM) on page 15 + Kernel memory object shows up + you know there are other formats for this document + nope .. i did not know that + in page 17 pmamp shows up + "the problems of external memory management" ? + braunr: the paper i am also reading is called x15mach_thesis + ah, that's mine + * sekon bows + :) + ok i see page 17 + so please good sir explain the relationship between kernel memory + object and pmap + (if any) + braunr: there is no mention of kernel memory object + again, i don't see any reference or definition of "kernel memory + object" + but your paper says + that when page faults occur + the kernel contact the manager for a kernel reference object + *memory + where ? + in section 2.1.3 (unless i read it wrong) + no just a sec + 2.1.5 + i never used the expression "kernel memory object" there :p + anyway, you're referring simple to memory objects as seen by + userspace pagers + a memory object is a data container + usually, it's a file + but it can be anything + the pager is the task that provides its content and implements the + object methods + as for the relation between them and the pmap module, it's a + distant one + i'll explain it with an example + page fault -> request content of memory object at a given offset + with given length from pager -> ask pmap to establish the mapping in the + mmu + braunr: thank you ver much + *very -- cgit v1.2.3