mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Ingo Molnar <mingo@elte.hu>, Eric Whiting <ewhiting@amis.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: -mmX 4G patches feedback [numbers: how much performance impact]
Date: Thu, 8 Apr 2004 23:59:46 +0200	[thread overview]
Message-ID: <20040408215946.GU31667@dualathlon.random> (raw)
In-Reply-To: <1479132704.1081405456@[10.10.2.4]>

On Wed, Apr 07, 2004 at 11:24:16PM -0700, Martin J. Bligh wrote:
> Instead of fiddling with tuning knobs, I'd prefer to just do the UKVA
> idea I've proposed before, and let each process have their own pagetables
> mapped permanently ;-)

that will have you pay for pte-highmem even in non-highmem machines.
I'm always been against your above idea ;) It can speedup mmap a bit for
some uncommon case but I believe your slowdown comes from the page faults after
exeve and startup not from mmap with the kernel compile, and worst of
all for non-highmem too (no sysctl or tuning knob can save you then).
Amittedly some mmap intensive workload can get a slight speedup compared
to pte-highmem but I don't think it's common and it has the potential of
slowing down the page faults especially in short lived tasks even w/o
highmem.

What I found attractive was the persistent kmap in userspace, but that
idea breaks with threading, and Andrew found another way that is to make
the page fault interruptible so it doesn't seem very worthwhile anymore
even w/o threading.

  reply	other threads:[~2004-04-08 21:59 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 16:36 -mmX 4G patches feedback Eric Whiting
2004-04-05 17:46 ` Andrea Arcangeli
2004-04-05 21:35   ` Eric Whiting
2004-04-05 22:16     ` Andrea Arcangeli
2004-04-06 11:55       ` -mmX 4G patches feedback [numbers: how much performance impact] Ingo Molnar
2004-04-06 14:49         ` Eric Whiting
2004-04-06 15:59         ` Andrea Arcangeli
2004-04-06 16:13           ` Arjan van de Ven
2004-04-06 16:39             ` Andrea Arcangeli
2004-04-06 17:24           ` Ingo Molnar
2004-04-06 17:57             ` Andrea Arcangeli
2004-04-07 22:54               ` Martin J. Bligh
2004-04-07 22:50                 ` Andrea Arcangeli
2004-04-06 19:25           ` Ingo Molnar
2004-04-06 20:25             ` Andrea Arcangeli
2004-04-07  6:03               ` Andrea Arcangeli
2004-04-07  6:46                 ` Ingo Molnar
2004-04-07  7:23                   ` Andrea Arcangeli
2004-04-07  8:23                     ` Ingo Molnar
2004-04-07 21:35                       ` Andrea Arcangeli
2004-04-07 17:27                   ` Andrea Arcangeli
2004-04-07  7:25               ` Ingo Molnar
2004-04-07 21:39                 ` Andrea Arcangeli
2004-04-07 22:58             ` Martin J. Bligh
2004-04-07 23:01               ` Andrea Arcangeli
2004-04-07 23:21                 ` Martin J. Bligh
2004-04-07 23:18                   ` Andrea Arcangeli
2004-04-07 23:34                     ` Martin J. Bligh
2004-04-08  0:18                       ` Andrea Arcangeli
2004-04-08  6:24                         ` Martin J. Bligh
2004-04-08 21:59                           ` Andrea Arcangeli [this message]
2004-04-08 22:19                             ` Martin J. Bligh
2004-04-08 22:19                               ` Andrea Arcangeli
2004-04-08 23:14                                 ` Martin J. Bligh
2004-04-08 23:22                                   ` Andrea Arcangeli
2004-04-08 23:42                                     ` Martin J. Bligh
2004-04-08 23:49                                       ` Andrea Arcangeli
2004-04-07 21:19       ` -mmX 4G patches feedback Martin J. Bligh
2004-04-07 21:49         ` Andrea Arcangeli
2004-04-06 17:59 -mmX 4G patches feedback [numbers: how much performance impact] Manfred Spraul
2004-04-06 18:41 ` Andrea Arcangeli

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=20040408215946.GU31667@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@osdl.org \
    --cc=ewhiting@amis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mingo@elte.hu \
    /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

Powered by JetHome