| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: XFS unhappy with large holey loopback and syncs |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Tue, 29 Nov 2005 16:21:48 +0100 |
| Cc: | Andi Kleen <ak@xxxxxxx>, David Chinner <dgc@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <438C70B3.5080709@xxxxxxx> |
| References: | <20051129003611.GF7209@xxxxxxxxxxxxxx> <20051129032937.GZ501696@xxxxxxxxxxxxxxxxx> <20051129091302.GB19515@xxxxxxxxxxxxx> <438C6B5D.1070604@xxxxxxx> <20051129145601.GF19515@xxxxxxxxxxxxx> <438C70B3.5080709@xxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
> Well, since it wants it as a single chunk of kernel memory..... that > gets hard to do in linux. Actually it probably has one large chunk and > is doing a realloc to get a larger chunk. For that it should use vmalloc - also no problem because it is backed in distributed order 0 4k pages. On 32bit the vmalloc space is a bit limited, but 8MB is still only a small part of it On x86-64 it's VmallocTotal: 34359738367 kB -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS unhappy with large holey loopback and syncs, Steve Lord |
|---|---|
| Next by Date: | Re: XFS unhappy with large holey loopback and syncs -- [OT] vmalloc 45-bit/32PiB address limit, Bryan J. Smith |
| Previous by Thread: | Re: XFS unhappy with large holey loopback and syncs, Steve Lord |
| Next by Thread: | Re: XFS unhappy with large holey loopback and syncs -- [OT] vmalloc 45-bit/32PiB address limit, Bryan J. Smith |
| Indexes: | [Date] [Thread] [Top] [All Lists] |