From: Ralf Baechle <ralf@linux-mips.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Kumar Gala <galak@kernel.crashing.org>,
Kyle McMartin <kyle@mcmartin.ca>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Only show RESOURCES_64BIT on relevant architectures
Date: Tue, 30 Oct 2007 11:42:21 +0000 [thread overview]
Message-ID: <20071030114221.GA24392@linux-mips.org> (raw)
In-Reply-To: <20071030083719.GJ32359@parisc-linux.org>
On Tue, Oct 30, 2007 at 02:37:19AM -0600, Matthew Wilcox wrote:
> On Mon, Oct 29, 2007 at 10:03:16PM -0500, Kumar Gala wrote:
> > The same is true on PPC32. Its a per platform thing. However, I'm
> > not sure if we could hide it from the user. There are cases on the
> > same HW platform that you want to run with just 32-bit phys (for
> > performance).
>
> Have you measured what the performance difference is?
Two identical kernel configs, one with one without CONFIG_RESOURCES_64BIT:
text data bss dec hex filename
3334684 152208 138624 3625516 37522c vmlinux
3340352 152464 138752 3631568 3769d0 vmlinux
So that's 5668, 256 bytes data and 128 bytes of bss for a total of 6052
bytes. Not a whole lot but I still fear some users on the most
claustrophobic systems will mind.
Ralf
next prev parent reply other threads:[~2007-10-30 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 20:15 [PATCH] Only show RESOURCES_64BIT on relevant architectures Kyle McMartin
2007-10-29 1:09 ` David Miller
2007-10-29 15:11 ` Kyle McMartin
2007-10-29 8:10 ` Russell King
2007-10-29 15:21 ` Kyle McMartin
2007-10-29 15:50 ` Russell King
2007-10-30 2:48 ` Ralf Baechle
2007-10-30 3:03 ` Kumar Gala
2007-10-30 8:37 ` Matthew Wilcox
2007-10-30 11:42 ` Ralf Baechle [this message]
2007-10-30 12:13 ` Matthew Wilcox
2007-10-30 14:14 ` Ralf Baechle
2007-10-30 20:00 ` Russell King
2007-10-30 14:19 ` Kumar Gala
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=20071030114221.GA24392@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=galak@kernel.crashing.org \
--cc=kyle@mcmartin.ca \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.