| To: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: %u-order allocation failed |
| From: | Pavel Machek <pavel@xxxxxxx> |
| Date: | Mon, 8 Oct 2001 16:44:37 +0000 |
| Cc: | Mikulas Patocka <mikulas@xxxxxxxxxxxxxxxxxxxxxxxx>, Rik van Riel <riel@xxxxxxxxxxxxxxxx>, Krzysztof Rusocki <kszysiu@xxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <E15qLzV-00071D-00@xxxxxxxxxxxxxxxxx>; from alan@xxxxxxxxxxxxxxxxxxx on Sun, Oct 07, 2001 at 11:01:45PM +0100 |
| References: | <Pine.LNX.3.96.1011007173411.6774A-100000@xxxxxxxxxxxxxxxxxxxxxxxx> <E15qLzV-00071D-00@xxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
Hi!
> > The difference between memory and vmalloc space is this: you fill up the
> > whole memory with cache => memory fragments. You don't fill up the whole
> > vmalloc space with anything => vmalloc space doesn't fragment.
>
> vmalloc space fragments. You fragment address space rather than pages thats
> all. Same problem
vmalloc space tends to be empty while ram tends to be full. That might be
important.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
|
| Previous by Date: | Debian journaling fs installation disks, Russel Ingram |
|---|---|
| Next by Date: | CONFIG_KDB_MODULES, Alan Eldridge |
| Previous by Thread: | Re: %u-order allocation failed, Rik van Riel |
| Next by Thread: | Re: %u-order allocation failed, Seth Mos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |