Talk:Page table

message: I just copied the relevant portions from Extended Page Table into this article under the section 'page table types'.  Please feel free to reject the change if I have changed too early.  —Preceding unsigned comment added by 207.46.55.29 (talk) 10:27, 24 September 2010 (UTC)
thread_title:  Combine [[Extended Page Table]] into this 

message: It seems to me that this page should be combined with the virtual memory page, or at the very least, a significant amount of material moved to that page.
Consider, in particular, the pictures at the start of the two articles.  They are almost identical (although the Page table picture is nicer).  It's clear that much of the same ground is covered in both places.
One possible way to factor the two articles would be to have the virtual memory article talk about the uses and policies of virtual memory, and leave the page table article to talk about the various actual implementations of page tables.  Unfortunately, that means the virtual memory article is going to end up being the FA candidate, and the page table article will be more technical and less accessible.
Iain McClatchie 00:08, 19 October 2005 (UTC)
replies: text: It's because of the nonsense that is the FAC process at the moment seems to favour nominators to somehow fully understand the subject at hand. Perhaps in desperation to get an actual technical article featured (gasp!) I bloated the article unnecessarily. I agree that a nice balance needs to be struck between the VM and the page table article. Maybe I'll even do it if I get a chance ;) Dysprosia 09:44, 19 October 2005 (UTC)
thread_title:  Combine with [[virtual memory]] 

message: During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!
* http://cne.gmu.edu/modules/vm/purple/ptable.html
** In Page table on Mon Jul 17 15:16:06 2006, 404 Not Found
** In Page table on Thu Jul 27 00:43:23 2006, 404 Not Found
----maru   (talk)  contribs 04:43, 27 July 2006 (UTC)
replies: text: That page now redirects to http://cs.gmu.edu/cne/modules/vm/purple/ptable.html. I've updated the article accordingly. Cheers, CWC(talk) 13:05, 5 September 2006 (UTC)
thread_title:  Dead link 

message: :Say we have a computer architecture where the word size is 32 bits. This means we are able to form addresses from 0x00000000 to 0xffffffff - spanning 4GB.
Something is wrong or at least missing here. I would rather rewrite the sentence the following way.
:Say we have a computer architecture with a 32 bit address bus. This means we are able to form addresses from 0x00000000 to 0xffffffff - spanning 4 Gi individual addresses, or 4 GiB when a single address contains 1 Byte.
I hope I'm correct. --Abdull 19:00, 20 November 2006 (UTC)
replies: text: I agree with you, this should be fixed. Asymmetric (talk) 11:16, 8 January 2008 (UTC)
thread_title:  Something missing? 

message: I made some drawings illustrating the address translation for x86 compatible processors. Perhaps you can use it for your article(s). :-)
Image:X86 Paging 4K.svg
Image:X86 Paging 4M.svg
Image:X86 Paging PAE 4K.svg
Image:X86 Paging PAE 2M.svg
--84.72.190.27 (talk) 12:01, 20 March 2008 (UTC)
thread_title:  Address translation illustrated for x86 

message: Virtual addressing is also an important solution to external fragmentation, am I right? Speedarius (talk) 03:05, 9 November 2008 (UTC)
thread_title:  Why virtual addressing 

message: I have read somewhere that the MMU will trigger a PF after not finding the page in the page table lookup, not after a TLB miss. As far as I understood it, after a TLB miss the MMU will go to the page table to look it up, and only after a miss there will trigger a PF. This is not what the text here says. Anyone wants to confirm or deny this?  —Preceding unsigned comment added by 93.173.172.11 (talk) 19:53, 24 April 2009 (UTC)
replies: text: This article is not a general description of address translation.  Certainly there are processor architectures that do far more address translation in hardware, without falling back so frequently on OS (kernal) intervention.  See, for example, descriptions of the IBM 370 (1970s era -- yes, TLBs are older than Intel and Microsoft!) or "ESA/390 Principles of Operation" at http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/dz9ar008/CCONTENTS.  A TLB miss on mainframes did not cause an interrupt, just hardware-managed table lookups. Evaluist (talk) 15:33, 8 May 2009 (UTC)
thread_title:  Page Fault Exception For TLB Miss? 

message: I suggest we merge the Extended Page Table article with this article.  --BwB (talk) 20:22, 29 July 2009 (UTC)
replies: text: Yes.  This article isn't about the x86 MMU, it's about page tables in general.  Discussing the general concept of a machine's VM support allowing a guest to directly manipulate its own page tables without trapping to the VM monitor might belong here, but specific details of one particular processor family's VM support, not so much (maybe if it covered, for example, support for it in multiple architectures, e.g. S/3x0 and x86). Guy Harris (talk) 06:55, 1 July 2012 (UTC)
thread_title: Merge Extended Page Table article with this article

message: Perhaps "frame" should be defined?  —Preceding unsigned comment added by 99.255.57.120 (talk) 01:12, 22 October 2009 (UTC)
thread_title:  Frame