From: "Jörn Engel" <joern@logfs.org>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Lasse Collin <lasse.collin@tukaani.org>,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
Tim Bird <tim.bird@am.sony.com>,
glp@openwrt.org, linux-embedded@vger.kernel.org
Subject: Re: LZMA inclusion
Date: Mon, 8 Dec 2008 21:17:34 +0100 [thread overview]
Message-ID: <20081208201734.GA4069@logfs.org> (raw)
In-Reply-To: <493C5D10.1040604@lougher.demon.co.uk>
On Sun, 7 December 2008 23:32:32 +0000, Phillip Lougher wrote:
>
> Currently, as mentioned above, Squashfs decompresses into a single
> contiguous output buffer. But, due to the linux kernel mailing list's
> dislike of vmalloc, this is being changed.
Don't blame lkml, blame Intel and IBM. Back in the days of the 386, a
beefy machine had 8MB of physical memory and 4GB of virtual memory
space. Noone had to worry about fragmentation anymore. If you needed a
1MB buffer, you'd just round up some 256 pages and instruct the mmu to
map them into a large contiguous address range in the virtual address
space. Life was good indeed.
But physical memory has constantly grown since, while the virtual memory
space has for a long time stagnated. Intel even introduced some
hardware hacks to use up to 64GB of physical memory with a measly 4GB of
virtual memory. Now it was _virtual_ memory fragmentation that you had
to worry about.
These days most CPUs you'd buy are 64bit, so virtual memory space has
become useful again. But as a kernel hacker, you have little control
over what hardware everyone is using. And those weird systems with
more physical than virtual memory are still around. :(
Jörn
--
Don't patch bad code, rewrite it.
-- Kernigham and Pike, according to Rusty
next prev parent reply other threads:[~2008-12-08 20:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 7:06 LZMA inclusion Gregers Petersen
2008-12-03 19:36 ` Tim Bird
2008-12-03 19:50 ` Florian Fainelli
2008-12-03 19:58 ` Bernhard Reutner-Fischer
2008-12-03 20:20 ` Sam Ravnborg
2008-12-03 20:45 ` Bernhard Reutner-Fischer
2008-12-03 21:16 ` Sam Ravnborg
2008-12-03 21:28 ` Bernhard Reutner-Fischer
2008-12-03 21:43 ` Sam Ravnborg
2008-12-03 21:48 ` Lasse Collin
2008-12-04 21:46 ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-05 8:31 ` Geert Uytterhoeven
2008-12-06 21:56 ` Lasse Collin
2008-12-07 16:01 ` Jörn Engel
2008-12-07 23:32 ` Phillip Lougher
2008-12-08 13:46 ` Jamie Lokier
2008-12-08 18:23 ` Lasse Collin
2008-12-08 19:00 ` Phillip Lougher
2008-12-09 10:20 ` Lasse Collin
2008-12-09 10:37 ` Geert Uytterhoeven
2008-12-16 8:55 ` Lasse Collin
2008-12-08 20:17 ` Jörn Engel [this message]
2008-12-08 21:47 ` Phillip Lougher
2008-12-08 22:15 ` Jörn Engel
2008-12-03 20:09 ` Gregers Petersen
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=20081208201734.GA4069@logfs.org \
--to=joern@logfs.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=glp@openwrt.org \
--cc=lasse.collin@tukaani.org \
--cc=linux-embedded@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
--cc=rep.dot.nop@gmail.com \
--cc=tim.bird@am.sony.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).