public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is it possible to use 8K page size on a i386 pc?
Date: Tue, 27 Aug 2002 17:26:05 -0700	[thread overview]
Message-ID: <3D6C189D.7080101@zytor.com> (raw)
In-Reply-To: 39B5C4829263D411AA93009027AE9EBB13299663@fmsmsx35.fm.intel.com

Luck, Tony wrote:
> H. Peter Anvin wrote:
> 
>>Followup to:  <200208271914.g7RJEQE07821@devserv.devel.redhat.com>
>>By author:    Pete Zaitcev <zaitcev@redhat.com>
>>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



  reply	other threads:[~2002-08-28  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28  0:19 Is it possible to use 8K page size on a i386 pc? Luck, Tony
2002-08-28  0:26 ` H. Peter Anvin [this message]
2002-09-10 16:34   ` Eric W. Biederman
     [not found] <mailman.1030474690.4302.linux-kernel2news@redhat.com>
2002-08-27 19:14 ` Pete Zaitcev
2002-08-28  0:06   ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2002-08-27 18:50 chen, xiangping
2002-08-27 19:19 ` Richard B. Johnson
2002-08-28  0:27 ` Daniel Phillips

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D6C189D.7080101@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox