mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com>
To: zaitcev@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: The IBM order relaxation patch
Date: Wed, 6 Feb 2002 22:50:29 +0100	[thread overview]
Message-ID: <OF5FF19417.595BC760-ONC1256B58.00762715@de.ibm.com> (raw)

Pete Zaitcev wrote:

> This patch is very s/390 specific and breaks all other architectures.
>  <<they meant "zSeries specific", surely --zaitcev>>

B.t.w. Martin found a way to make the patch less intrusive so
that it won't break other archs any more ...

>It's a stupid question, but: why can we not simply
>wait until a desired unfragmented memory area is available,
>with a GPF flag? What they describe does not happen in an
>interrupt context, so we can sleep.

Because nobody even *tries* to free adjacent pages to build up
a free order-2 area.  You could wait really long ...

This looks hard to fix with the current mm layer.  Maybe Rik's
rmap method could help here, because with reverse mappings we
can at least try to free adjacent areas (because we then at least
*know* who's using the pages).

>And another one: why not to increase a kernel-visible or "soft"
>page size to 16KB for zSeries? It's a 64 bits platform. There
>will be some increase in fragmentation, but nobody measured it.
>Perhaps it's not going to be severe. It may even improve paging
>efficiency.

Because then we can mmap() to user space only on 16KB boundaries.
This is a problem in particular for the 31-bit emulation layer,
as 31-bit binaries are laid out on 4KB boundaries by the linker,
so you really need to be able to mmap() on 4KB boundaries.

One way to fix this could be to allow user space mappings on a
different granularity than the 'page size' for the allocator.
(Is this what PAGE_SIZE vs. PAGE_CACHE_SIZE had been intended
for, maybe?  It doesn't work at the moment in any case.)


Mit freundlichen Gruessen / Best Regards

Ulrich Weigand

--
  Dr. Ulrich Weigand
  Linux for S/390 Design & Development
  IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
  Phone: +49-7031/16-3727   ---   Email: Ulrich.Weigand@de.ibm.com


             reply	other threads:[~2002-02-06 21:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06 21:50 Ulrich Weigand [this message]
2002-02-07  0:18 ` Alan Cox
2002-02-07  4:01 ` David S. Miller
2002-02-07 12:16   ` Rik van Riel
2002-02-07 12:29   ` David S. Miller
2002-02-07 12:42     ` Rik van Riel
2002-02-07 12:58     ` Hugh Dickins
2002-02-07 14:12 ` Daniel Phillips
2002-02-07 14:55   ` Rik van Riel
2002-02-07 15:07     ` Daniel Phillips
2002-02-07 15:10     ` David S. Miller
2002-02-09 20:21   ` Alex Bligh - linux-kernel
  -- strict thread matches above, loose matches on Subject: below --
2002-02-07 15:05 Ulrich Weigand
2002-02-07 15:13 ` Rik van Riel
2002-02-07 17:57 ` Daniel Phillips
2002-02-06 19:13 Pete Zaitcev

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=OF5FF19417.595BC760-ONC1256B58.00762715@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.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

all inboxes | Powered by JetHome®