Eric Lowe wrote: > Holger Berger wrote: > >> To make matters worse, Solaris (unlike many other > >> OS's) ties page_t structures to particular physical > >> addresses, and there is plenty of code that assumes > >> p_pagenum can't change even if the page isn't locked. > >> This complicates the issues of separating out the > >> "page size" the user sees and the "page size" the > >> kernel is using to manage physical memory. > > > > I assume this is no problem when the default page size is equal to the > > minimum page size supported by the kernel. > > A kernel which only supports 64k+ page sizes will avoid page_t related > > headaches . > > That's correct, though there were some pretty sticky issues with MAXBSIZE > since the filesystems (UFS, probably others) assume (wrongly) that > MAXBSIZE is PAGESIZE. Obviously when you up the PAGESIZE this isn't true > anymore, so some code had to be added to make the filesystem understand > that a page doesn't hold a single block, but can hold multiple blocks.
How does UFS on i386 deal with this problem ? AFAIK x86 has 4k pages by default and only half the size of |MAXBSIZE| ... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
