public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gérard Roudier" <groudier@free.fr>
To: Hugh Dickins <hugh@veritas.com>
Cc: "David S. Miller" <davem@redhat.com>, <anton@samba.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] small sym-2 fix
Date: Thu, 15 Nov 2001 21:22:09 +0100 (CET)	[thread overview]
Message-ID: <20011115205859.B2340-100000@gerard> (raw)
In-Reply-To: <Pine.LNX.4.21.0111152105500.1588-100000@localhost.localdomain>



On Thu, 15 Nov 2001, Hugh Dickins wrote:

> On Thu, 15 Nov 2001, Gérard Roudier wrote:
> >
> > To be serious, the right fix is to have some logical page be some power of
> > two of the physical page when the physical page is too small. Can we hope
> > Linux-2.5 to allow this?
>
> It's certainly doable.  I have an i386 patch against 2.4.7 which did that,
> MMUPAGE_SIZE 4kB distinguished from PAGE_SIZE 4kB, 8kB, 16kB or 32kB
> (but 64kB truncates to 0 in unsigned short b_size, doesn't work so well!);
> while still presenting the 4kB EXEC_PAGESIZE to userspace.
>
> It's a bit tedious working through each kernel update, to decide which
> PAGEs should be MMUPAGEs etc, and I didn't see an immediate reward of
> a huge leap in performance, so I haven't kept it up to date since then.

Think about portable _software_ as large parts of the kernel that have to
cope with very different _hardware_ allocation granularities depending on
targetted platforms. This led and still leads to useless complexity in
many places. Apart this that will require to modify the kernel code in
order to gain full advantage of a new larger page size, you will get some
not negligible immediate reward on IA32, as for example fork() to be
really unlikely to fail on loaded machines, etc..., etc...

  Gérard.


  reply	other threads:[~2001-11-15 23:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15  4:36 [PATCH] small sym-2 fix Anton Blanchard
2001-11-15 10:19 ` David S. Miller
2001-11-15 11:35   ` Anton Blanchard
2001-11-15 11:41     ` David S. Miller
2001-11-15 12:17       ` Anton Blanchard
2001-11-15 16:27 ` Gérard Roudier
2001-11-15 19:26   ` David S. Miller
2001-11-15 18:07     ` Gérard Roudier
2001-11-15 21:22       ` Hugh Dickins
2001-11-15 20:22         ` Gérard Roudier [this message]
2001-11-15 19:46   ` Gérard Roudier
2001-11-15 22:39     ` David S. Miller
2001-11-15 20:41       ` Gérard Roudier
2001-11-15 22:44       ` David S. Miller
2001-11-20  6:02     ` Anton Blanchard
2001-11-20 17:26       ` Gérard Roudier
2001-11-21  2:19         ` Anton Blanchard
2001-11-21  3:49           ` David S. Miller
2001-11-21 17:19           ` Gérard Roudier
2001-11-22  5:19             ` Paul Mackerras

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=20011115205859.B2340-100000@gerard \
    --to=groudier@free.fr \
    --cc=anton@samba.org \
    --cc=davem@redhat.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    /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