On Tue, Jan 17, 2006 at 11:18:56PM +0100, Poul-Henning Kamp wrote: > In message <43CD612E.2060002@xxxxxxxxxxxx>, Julian Elischer writes:
> >Jeff Roberson wrote:
> >
> >> I have implemented support in the vm for PAGE_SIZE values which are a
> >> multiple of the hardware page size. This is primarily useful for two
> >> things:
> >
> >Mach (and the VM system we inherrited from it) had this. I beieve it was
> >removed with teh comment
> >"If we need this and someone is willing to support it it can be added
> >back" .
>
> It was a VAX artifact and not very usable. I belive we have a couple
> of comments and macros which still talk about "clicks".
>
It was not a VAX artifact. Also, Jeff's work differs significantly
from what Mach did on the VAX. I'll explain the differences after
my paper deadline passes tomorrow.
Alan
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
Re: Large virtual page size support. ... multiple of the hardware page size. ... This is primarily useful for two things: ... I beieve it was removed with teh comment ... I can't see any record of it in our CVS files but I distinctly remember it in MACH.... (freebsd-arch)
Re: Large virtual page size support. ... sizes, one being the native, hardware page size and the other being a larger, abstract page size. ... The essential difference between Jeff's patch and what Mach did on the VAX is that Mach's use of the native, hardware page size was entirely within the pmap and locore-level code. ... as far as the machine-independent layer of the Mach kernel was concerned the page size was 4K bytes. ... Consequently, the ABI documents that I've seen don't specify a particular page size only that 64K bytes is the largest that a page will ever be; to learn the precise page size, they say that you must call the OS at run time. ... (freebsd-arch)
Re: Large virtual page size support. ... sizes, one being the native, hardware page size and the other being a larger, abstract page size. ... The essential difference between Jeff's patch and what Mach did on the VAX is that Mach's use of the native, hardware page size was entirely within the pmap and locore-level code. ... as far as the machine-independent layer of the Mach kernel was concerned the page size was 4K bytes. ... I don't recall any other pmap implementations having different native and abstract page sizes.... (freebsd-arch)
Re: Large virtual page size support. ... sizes, one being the native, hardware page size and the other being a larger, abstract page size. ... The essential difference between Jeff's patch and what Mach did on the VAX is that Mach's use of the native, hardware page size was entirely within the pmap and locore-level code. ... as far as the machine-independent layer of the Mach kernel was concerned the page size was 4K bytes. ... I don't recall any other pmap implementations having different native and abstract page sizes.... (freebsd-arch)
Re: Large virtual page size support. ... sizes, one being the native, hardware page size and the other being a larger, abstract page size. ... The essential difference between Jeff's patch and what Mach did on the VAX is that Mach's use of the native, hardware page size was entirely within the pmap and locore-level code. ... as far as the machine-independent layer of the Mach kernel was concerned the page size was 4K bytes. ... I don't recall any other pmap implementations having different native and abstract page sizes.... (freebsd-arch)
