LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCHv3 1/3] x86: use ELF format in compressed images.
Date: Sun, 06 Apr 2008 11:22:24 +0100	[thread overview]
Message-ID: <1207477344.28696.25.camel@localhost.localdomain> (raw)
In-Reply-To: <86802c440804060003q43f14122vd527514daf77cb89@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]


On Sun, 2008-04-06 at 00:03 -0700, Yinghai Lu wrote:
> so will cost every bzImage extra memory copy? that could be 18M or
> even more big.

Is it a huge deal for something that happens exactly once on boot? How
does the time take compare with the time to do the decompression?

18M seems like an awfully large kernel image to me. My distro (Debian)
kernel is more like 3M uncompressed. If someone was interested in fast
booting presumably they would either build a kernel with exactly what
they need.

> wonder if can have one some other kind elf format, and offset load
> address to avoid that mem copy.

I guess you could reduce the load address by sizeof(headers) and add a
dest == (output + phdr->p_offset) test before the copy.

Another possibility, which is much more complex, is that the ELF parsing
could be integrated into the decompressor such that the data is
decompressed into the correct location directly.

Ian.

-- 
Ian Campbell

People who have no faults are terrible; there is no way of taking
advantage of them.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-06 10:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 20:54 [PATCHv3 0/3] x86: boot protocol updates Ian Campbell
2008-02-13 20:54 ` [PATCHv3 1/3] x86: use ELF format in compressed images Ian Campbell
2008-02-13 20:54   ` [PATCHv3 2/3] x86: add a crc32 checksum to the kernel image Ian Campbell
2008-02-13 20:55     ` [PATCHv3 3/3] x86: bump image header to version 2.08 Ian Campbell
2008-02-14 11:34   ` [PATCHv3 1/3] x86: use ELF format in compressed images Mark McLoughlin
2008-02-14 17:01     ` Ian Campbell
2008-02-14 17:37       ` Mark McLoughlin
2008-02-14 17:51         ` Ian Campbell
2008-02-14 17:57       ` Ian Campbell
2008-02-14 21:10         ` Jeremy Fitzhardinge
2008-02-14 21:14           ` H. Peter Anvin
2008-02-15  6:37             ` Jeremy Fitzhardinge
2008-02-14 18:29       ` Ian Campbell
2008-02-14 18:30       ` H. Peter Anvin
2008-04-06  7:03   ` Yinghai Lu
2008-04-06 10:22     ` Ian Campbell [this message]
2008-04-06 16:38     ` H. Peter Anvin
2008-04-06 17:19       ` Yinghai Lu
2008-04-06 17:25         ` H. Peter Anvin
2008-04-06 17:34           ` Yinghai Lu
2008-02-17 14:04 ` [PATCHv3 0/3] x86: boot protocol updates Thomas Gleixner
2008-02-19  8:16   ` Ian Campbell

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=1207477344.28696.25.camel@localhost.localdomain \
    --to=ijc@hellion.org.uk \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=yhlu.kernel@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).