From: "H. Peter Anvin" <hpa@zytor.com>
To: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
Cc: Olivier Galibert <galibert@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Is the x86-64 kernel size limit real?
Date: Thu, 22 Jun 2006 14:39:03 -0700 [thread overview]
Message-ID: <449B0DF7.5000407@zytor.com> (raw)
In-Reply-To: <449B355C.2080805@aladin.ro>
Eduard-Gabriel Munteanu wrote:
> *This message was transferred with a trial version of CommuniGate(r) Pro*
> Olivier Galibert wrote:
>
>>
>> which shows two things:
>> 1- a8f5034540195307362d071a8b387226b410469f should have a x86-64 version
>> 2- the limit looks entirely artificial
>>
>> So, is removing the limit prone to bite me?
>>
>> OG.
>
> The build system merely tries to warn you it's not going to fit on a
> floppy disk. "bzImage" means "Big zImage", not "bz2-compressed Image",
> so unless you're building a floppy disk, don't use zImage.
>
He's talking about the bzImage limit, not the zImage limit. The bzImage limit in x86-64
is real (in the sense it exists) but incorrect (in the sense that it has the wrong value);
see my other post.
-hpa
next prev parent reply other threads:[~2006-06-22 21:39 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 [this message]
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
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=449B0DF7.5000407@zytor.com \
--to=hpa@zytor.com \
--cc=galibert@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxdamage@aladin.ro \
/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