public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel too big
Date: Thu, 19 Feb 2004 17:04:13 -0800	[thread overview]
Message-ID: <40355D0D.3010800@transmeta.com> (raw)
In-Reply-To: <UTC200402200021.i1K0L1525525.aeb@smtp.cwi.nl>

Andries.Brouwer@cwi.nl wrote:
> In 2.5.61 hpa changed
> 
> -      /* 0x28000*16 = 2.5 MB, conservative estimate for the current maximum */
> -      if (sys_size > (is_big_kernel ? 0x28000 : DEF_SYSSIZE))
> +      /* 0x40000*16 = 4.0 MB, reasonable estimate for the current maximum */
> +      if (sys_size > (is_big_kernel ? 0x40000 : DEF_SYSSIZE))
>               die("System is too big. ...");
> 
> (with comment "bootsect removal").
> 
> Today I find for a 2.6.3 machine that it boots with 2994 kB and
> crashes at boot time with 3005 kB.
> 
> Thus, it looks like this "reasonable estimate" is too optimistic.
> 
> If I understand correctly, the real requirement is that
> _end must stay below 8MB (unless the initial page tables
> in head.S are made larger). A crash occurs with _end = c07fcf8c.
> 
> Maybe these "conservative" or "reasonable" estimates should be
> replaced by a text on _end?
> 

What we should do is to actually look at the limit that matters.

Also, if the limit really is around 3 MB compressed we probably need to
extend it to 16 MB uncompressed; we're a little too close for comfort.


  reply	other threads:[~2004-02-20  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20  0:21 kernel too big Andries.Brouwer
2004-02-20  1:04 ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-20 14:00 Andries.Brouwer
2004-02-20 20:45 ` H. Peter Anvin
2004-02-21  4:14   ` H. Peter Anvin

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=40355D0D.3010800@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=Andries.Brouwer@cwi.nl \
    --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