From: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rohit Seth <rohit.seth@intel.com>, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH] Increase number of e820 entries hard limit from 32 to 128
Date: Fri, 22 Apr 2005 19:32:50 -0700 [thread overview]
Message-ID: <20050422193250.A18512@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504221851140.2344@ppc970.osdl.org>; from torvalds@osdl.org on Fri, Apr 22, 2005 at 06:51:59PM -0700
On Fri, Apr 22, 2005 at 06:51:59PM -0700, Linus Torvalds wrote:
> On Fri, 22 Apr 2005, Venkatesh Pallipadi wrote:
> > The specifications that talk about E820 map doesn't have an upper limit
> > on the number of E820 entries. But, today's kernel has a hard limit of 32.
> > With increase in memory size, we are seeing the number of E820 entries
> > reaching close to 32. Patch below bumps the number upto 128.
>
> Hmm. Anything that changes setup.S tends to have bootloader dependencies.
> I worry whether this one does too..
>
The setup.S change in this patch should be OK. As it is adding to the
existing zero-page and keeping it within one page. I tested it on systems
with grub, adding some dummy E820 entries and it worked fine.
However, there is another place that needs to be changed. Boot loaders
also calls E820 while booting directly with vmlinux (instead of usual
bzImage - which is handled by this patch) and that needs to change to
incorporate more E820 entries. But, there we may need more changes, to
the boot protocol version and the like. On a side note, looking at the
grub source, it seems to have a limit of 50 entries today, which doesn't
agree with current 32 entry limit in the kernel. Not sure why grub has
this different limit though.
Thanks,
Venki
next prev parent reply other threads:[~2005-04-23 2:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 1:14 Venkatesh Pallipadi
2005-04-22 23:52 ` jmerkey
2005-04-23 1:51 ` Linus Torvalds
2005-04-23 2:32 ` Venkatesh Pallipadi [this message]
2005-04-23 15:10 ` Andi Kleen
2005-04-27 0:40 ` Venkatesh Pallipadi
2005-06-06 10:45 ` Boot problems & zero page Was: " David Balažic
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=20050422193250.A18512@unix-os.sc.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rohit.seth@intel.com \
--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 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®