public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Is the x86-64 kernel size limit real?
Date: Sun, 25 Jun 2006 10:19:52 -0700 (PDT)	[thread overview]
Message-ID: <e7mgjo$oco$1@terminus.zytor.com> (raw)
In-Reply-To: p73hd2cnik6.fsf@verdi.suse.de

Followup to:  <p73hd2cnik6.fsf@verdi.suse.de>
By author:    Andi Kleen <ak@suse.de>
In newsgroup: linux.dev.kernel
>
> Olivier Galibert <galibert@pobox.com> writes:
> 
> > I get bitched at by the build process because the kernel I get is
> > around 4.5Mb compressed.  i386 does not have that limitation.
> > Interestingly, a diff between the two build.c gives:
> 
> A patch to fix it is already queued for 2.6.18
> 
> Also long term it might be completely dropped when the uncompressor
> moves to long mode.
> 

It can be completely dropped now (and the directories unified); the
size limitation on the uncompressed size can be enforced in the linker
script.

The uncompressor only needs to be in long mode to support > 4 GB.

	-hpa


      reply	other threads:[~2006-06-25 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 20:46 Is the x86-64 kernel size limit real? Olivier Galibert
2006-06-22 21:38 ` H. Peter Anvin
2006-06-22 22:00   ` Olivier Galibert
2006-06-22 22:45     ` H. Peter Anvin
2006-06-22 23:02       ` Olivier Galibert
2006-06-23  0:27 ` Eduard-Gabriel Munteanu
2006-06-22 21:39   ` H. Peter Anvin
2006-06-22 21:52   ` Olivier Galibert
2006-06-23  1:18     ` Eduard-Gabriel Munteanu
2006-06-23 12:49 ` Andi Kleen
2006-06-25 17:19   ` H. Peter Anvin [this message]

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='e7mgjo$oco$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --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