Hi,
I just wonder how PAGE_SIZE in determined in each architecture? Is it
possible to use 8k or bigger page size in a i386 PC?
Thanks,
Xiangping
>[...]
> I just wonder how PAGE_SIZE in determined in each architecture? Is it
> possible to use 8k or bigger page size in a i386 PC?
>
> Thanks,
> Xiangping
You may run into trouble with something that calls mmap with
a fixed address, with executables which have text sizes of
odd number of small pages. I was told that these problems are
fairly rare.
Running a bigger page size does nothing to help your TLB
coverage, but it might improve paging performance (or
it might not).
-- Pete
On Tue, 27 Aug 2002, chen, xiangping wrote:
> Hi,
>
> I just wonder how PAGE_SIZE in determined in each architecture? Is it
> possible to use 8k or bigger page size in a i386 PC?
>
> Thanks,
>
> Xiangping
It's hardware; "Because both the virtual pages in the linear
address space and the physical pages of memory are aligned to
4k page boundaries, there is no need to modify the low 12
bits of the address. These 12 bits pass straight through the
paging hardware, whether paging is enabled or not...."
Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
The US military has given us many words, FUBAR, SNAFU, now ENRON.
Yes, top management were graduates of West Point and Annapolis.
Followup to: <[email protected]>
By author: Pete Zaitcev <[email protected]>
In newsgroup: linux.dev.kernel
>
> You may run into trouble with something that calls mmap with
> a fixed address, with executables which have text sizes of
> odd number of small pages. I was told that these problems are
> fairly rare.
>
Only 50% of all binaries are affected... that's fairly rare :)
-hpa
--
<[email protected]> at work, <[email protected]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <[email protected]>
H. Peter Anvin wrote:
> Followup to: <[email protected]>
> By author: Pete Zaitcev <[email protected]>
> In newsgroup: linux.dev.kernel
> >
> > You may run into trouble with something that calls mmap with
> > a fixed address, with executables which have text sizes of
> > odd number of small pages. I was told that these problems are
> > fairly rare.
> >
>
> Only 50% of all binaries are affected... that's fairly rare :)
The majority of x86 linux binaries run on ia64 with a 16K
pagesize (admittedly with some not-so-pretty code to fudge
mmap/munmap addresses ... but it is proof that you can reduce
the problems to "fairly rare").
-Tony
Luck, Tony wrote:
> H. Peter Anvin wrote:
>
>>Followup to: <[email protected]>
>>By author: Pete Zaitcev <[email protected]>
>>In newsgroup: linux.dev.kernel
>>
>>>You may run into trouble with something that calls mmap with
>>>a fixed address, with executables which have text sizes of
>>>odd number of small pages. I was told that these problems are
>>>fairly rare.
>>
>>Only 50% of all binaries are affected... that's fairly rare :)
>
> The majority of x86 linux binaries run on ia64 with a 16K
> pagesize (admittedly with some not-so-pretty code to fudge
> mmap/munmap addresses ... but it is proof that you can reduce
> the problems to "fairly rare").
>
It's proof that you can kluge around it. Part of the issue is with the
handling of the code versus data segment, which means you have to treat
(part of) the code segment as data.
Changing the i386 port to use > 4K pages would have to go through
similar contortions.
-hpa
On Tuesday 27 August 2002 20:50, chen, xiangping wrote:
> Hi,
>
> I just wonder how PAGE_SIZE in determined in each architecture? Is it
> possible to use 8k or bigger page size in a i386 PC?
Hi,
It's possible, but we haven't gotten around to implementing it yet ;-)
--
Daniel
"H. Peter Anvin" <[email protected]> writes:
> Luck, Tony wrote:
> > H. Peter Anvin wrote:
> >
> >>Followup to: <[email protected]>
> >>By author: Pete Zaitcev <[email protected]>
> >>In newsgroup: linux.dev.kernel
> >>
> >>>You may run into trouble with something that calls mmap with
> >>>a fixed address, with executables which have text sizes of
> >>>odd number of small pages. I was told that these problems are
> >>>fairly rare.
> >>
> >>Only 50% of all binaries are affected... that's fairly rare :)
> >
> > The majority of x86 linux binaries run on ia64 with a 16K
> > pagesize (admittedly with some not-so-pretty code to fudge
> > mmap/munmap addresses ... but it is proof that you can reduce
> > the problems to "fairly rare").
> >
>
> It's proof that you can kluge around it. Part of the issue is with the
> handling of the code versus data segment, which means you have to treat
> (part of) the code segment as data.
>
> Changing the i386 port to use > 4K pages would have to go through
> similar contortions.
In particular the sysv ABI for i386 specifies a 4K page size be
supported.
The alpha ABI (which planned for page size changes) specifies all data
in binaries must be 64K aligned. Despite initially shipping with
something smaller. This issue is particularly important to demand
paging.
The classic work around is to just read the entire binary into memory
and don't worry about sharing pages. Which is an effective way to support
old a.out binaries, that had 1K alignments.
The case of mmap(MAP_FIXED) without the proper alignment can only
fail. And of course libc would need to be updated so that
getpagesize() returns the appropriate page size.
But be very clear that anything that changes the externally visible
page size is an ABI change, and best avoided.
But note it should be possible to grow he kernels internal page size
without making it externally visible. And allow mappings of partial
pages. So far it has been more trouble than it is worth.
Eric