From: Rene Herman <rene.herman@keyaccess.nl>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, akpm@osdl.org, mingo@elte.hu
Subject: Re: Patch to reorder functions in the vmlinux to a defined order
Date: Thu, 23 Feb 2006 20:23:06 +0100 [thread overview]
Message-ID: <43FE0B9A.40209@keyaccess.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0602230902230.3771@g5.osdl.org>
Linus Torvalds wrote:
> The same should be true on x86, btw. Where we should use a physical start
> address of 4MB for best performance.
Does 16MB still work? Gets the kernel out of the old ZONE_DMA. I suppose
not many people are really using that anyway anymore these days, but if
no downsides maybe?
Also, did the kernel still boot on a 4M machine, and would it still do
so with the change to 4M as posted? 2.4 used to boot fine with 4M. Not
certain anymore if I ever tested that with 2.6 (and can't right now).
Rene.
next prev parent reply other threads:[~2006-02-23 19:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 13:19 Patch to make the head.S-must-be-first-in-vmlinux order explicit Arjan van de Ven
2006-02-23 13:42 ` Andi Kleen
2006-02-23 13:57 ` Arjan van de Ven
2006-02-23 14:14 ` Andi Kleen
2006-02-23 14:40 ` Arjan van de Ven
2006-02-24 13:49 ` Eric W. Biederman
2006-02-24 13:53 ` Arjan van de Ven
2006-02-24 14:17 ` Eric W. Biederman
2006-02-24 14:32 ` Andi Kleen
2006-02-23 15:09 ` Patch to reorder functions in the vmlinux to a defined order Arjan van de Ven
2006-02-23 16:00 ` Andi Kleen
2006-02-23 16:02 ` Arjan van de Ven
2006-02-23 16:43 ` Arjan van de Ven
2006-02-23 16:48 ` Andi Kleen
2006-02-23 16:49 ` Arjan van de Ven
2006-02-23 17:08 ` Linus Torvalds
2006-02-23 17:20 ` Andi Kleen
2006-02-23 17:34 ` Alan Cox
2006-02-23 18:13 ` Andi Kleen
2006-02-23 17:44 ` Linus Torvalds
2006-02-23 18:14 ` Andi Kleen
2006-02-23 19:03 ` linux-os (Dick Johnson)
2006-02-23 19:32 ` Linus Torvalds
2006-02-24 12:43 ` linux-os (Dick Johnson)
2006-02-23 19:23 ` Rene Herman [this message]
2006-02-23 19:31 ` Andi Kleen
2006-02-23 19:34 ` Alan Cox
2006-02-23 19:48 ` Rene Herman
2006-02-23 19:35 ` Linus Torvalds
2006-02-23 19:44 ` Arjan van de Ven
2006-02-23 20:13 ` Rene Herman
2006-02-23 20:26 ` Dave Jones
2006-02-24 2:44 ` Fernando Luis Vazquez Cao
2006-02-24 2:47 ` Andi Kleen
2006-02-24 14:44 ` Theodore Ts'o
2006-02-23 23:19 ` Linus Torvalds
2006-02-23 23:53 ` Rene Herman
2006-02-24 14:23 ` Eric W. Biederman
2006-02-24 14:23 ` Eric W. Biederman
2006-02-24 15:30 ` Rene Herman
2006-02-24 15:55 ` Eric W. Biederman
2006-02-24 16:48 ` Andi Kleen
2006-02-24 20:38 ` Eric W. Biederman
2006-02-25 2:11 ` Folkert van Heusden
2006-02-25 8:32 ` Arjan van de Ven
2006-02-24 17:26 ` Linus Torvalds
2006-02-24 17:57 ` Rene Herman
2006-02-24 18:11 ` Linus Torvalds
2006-03-07 23:36 ` H. Peter Anvin
2006-02-24 14:11 ` Eric W. Biederman
2006-02-24 1:38 ` Martin Bligh
2006-02-23 20:07 ` Andy Whitcroft
2006-02-23 16:48 ` Linus Torvalds
2006-02-23 16:54 ` Benjamin LaHaise
2006-02-23 18:01 ` Arjan van de Ven
2006-02-23 16:57 ` linux-os (Dick Johnson)
2006-02-23 17:36 ` Zwane Mwaikambo
2006-02-23 17:59 ` Arjan van de Ven
2006-02-24 22:19 ` Tony Luck
2006-02-24 22:21 ` Arjan van de Ven
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=43FE0B9A.40209@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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 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.