Re: It's time to get rid of zImage

• Next message: Alan Cox: "Re: Semi up to date JOBS list"
• Previous message: Mike Galbraith: "Re: loop device deadlocks"
• In reply to: H. Peter Anvin: "It's time to get rid of zImage"
• Next in thread: Hans Lermen: "Re: It's time to get rid of zImage"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

H. Peter Anvin wrote:
> ---> It's time to get rid of zImage once and for all. <---

Personally, I wouldn't cry to hard for zImage. But as has been said,
please not before 2.5.

BTW, I'm sure a few people will wonder whether this doesn't raise
the minimum amount of memory into which you can squeeze a kernel.
Fortunately, the answer is "no".

Given compressed size N and compression factor C, we get accesses
to the following maximum addresses (ignoring heaps, initrd, and all
that):

zImage: max_z = 1MB+C*N
bzImage: max_bz = 1MB+N+C*N-0x8e000

So max_bz > max_z <=> N > 0x8e000. Since zImage limits the size of
the compressed kernel to 0x80000 bytes, this can never happen.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, ICA, EPFL, CH       werner.almesberger@ica.epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Alan Cox: "Re: Semi up to date JOBS list"
• Previous message: Mike Galbraith: "Re: loop device deadlocks"
• In reply to: H. Peter Anvin: "It's time to get rid of zImage"
• Next in thread: Hans Lermen: "Re: It's time to get rid of zImage"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:30 EST