From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: -mmX 4G patches feedback [numbers: how much performance impact]
Date: Thu, 08 Apr 2004 16:42:37 -0700 [thread overview]
Message-ID: <39780000.1081467757@flay> (raw)
In-Reply-To: <20040408232215.GY31667@dualathlon.random>
--On Friday, April 09, 2004 01:22:15 +0200 Andrea Arcangeli <andrea@suse.de> wrote:
> On Thu, Apr 08, 2004 at 04:14:08PM -0700, Martin J. Bligh wrote:
>> Me confused. Are you saying it's worse compared to pte_highmem? or to
>> shoving ptes in lowmem?
>
> worse than pte_highmem if booting with mem=800m
>
>> Ah. You're worried about the distro situation, where PTE_HIGHMEM would
>> be turned on for a non-highmem machine, right? Makes more sense I guess.
>
> it's not just a distro situation, it's about not having to recompile the
> kernel for every machine I own, even gentoo has an option to have a
> compile server in the network that build packages and you install the
> binaries from it, so there must be some value in being able to share a
> binary on more than one machine (this is especially true for me since I
> upgrade kernel quite fast).
>
> it's not just about non-highmem machines, on 1G/2G boxes the probability
> that pte-highmem cause you any slowdown is an order of magnitude smaller
> than on a 32G machine (where ptes should never hit lowmem or it means my
> classzone lowmem_reserve_ratio algorithms have not yet been ported to 2.6)
> with your model you'd have no way to boost when you are lucky to get a
> lowmem page.
OK, I think I understand your concern now - I was being slow ;-)
I guess there are a few more PTEs to set up on exec, you're right.
I still think it's faster than pte_highmem, which was a static config
option anyway (so it's better in all cases than pte_highmem, when enabled)
but still not perfect. Hmm. I'll go think about it ;-)
m.
next prev parent reply other threads:[~2004-04-08 23:31 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
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 [this message]
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=39780000.1081467757@flay \
--to=mbligh@aracnet.com \
--cc=andrea@suse.de \
--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
Powered by JetHome