| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: XFS unhappy with large holey loopback and syncs -- [OT] vmalloc 45-bit/32PiB address limit |
| From: | "Bryan J. Smith" <b.j.smith@xxxxxxxx> |
| Date: | Tue, 29 Nov 2005 07:31:33 -0800 (PST) |
| Cc: | Andi Kleen <ak@xxxxxxx>, David Chinner <dgc@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20051129152148.GH19515@xxxxxxxxxxxxx> |
| Reply-to: | b.j.smith@xxxxxxxx |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
Andi Kleen <ak@xxxxxxx> wrote: > 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 If I'm reading that correctly, that's 45-bit/32PiB addressing. Where does that limit come from? Is that the limit of Linux's new, 4-level page table logic in x86-64 (the old 3-level page table being capable of 39-bit/512GiB), or is it something else? Just curious. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@xxxxxxxx | (please excuse any http://thebs413.blogspot.com/ | missing headers) |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS unhappy with large holey loopback and syncs, Andi Kleen |
|---|---|
| Next by Date: | Re: XFS unhappy with large holey loopback and syncs -- [OT] vmalloc 45-bit/32PiB address limit, Andi Kleen |
| Previous by Thread: | Re: XFS unhappy with large holey loopback and syncs, Andi Kleen |
| Next by Thread: | Re: XFS unhappy with large holey loopback and syncs -- [OT] vmalloc 45-bit/32PiB address limit, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |