| |||||||||||
Solution in silicon?Solution in silicon?Posted Jul 19, 2003 6:34 UTC (Sat) by giraffedata (subscriber, #1954)In reply to: Solution in silicon? by proski Parent article: 64GB on 32-bit systems
There's a more robust solution. No need to make the address translation sensitive to kernel vs user space. Address spaces are just address spaces. The TLB should include an address space ID in its translations. Then you wouldn't purge the TLB just because you switch address spaces. You could switch between user and kernel space and between processes, all with the TLB still warm.
(Log in to post comments)
Solution in silicon? Posted Jul 19, 2003 23:25 UTC (Sat) by tjc (guest, #137) [Link] That sounds like a good idea. I can't find much info on it though. My OS book has about two paragraphs on address space identifiers, and googling for "ASID" brings up a page for the American Society of Interior Designers. ;-)
|
|||||||||||