| To: | "John Hawkes" <hawkes@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: more mips64 vmalloc() space |
| From: | Ralf Baechle <ralf@xxxxxxxxxxx> |
| Date: | Tue, 13 Mar 2001 01:49:21 +0100 |
| Cc: | linux-origin@xxxxxxxxxxx |
| In-reply-to: | <004001c0ab55$da882820$6701a8c0@marin1.sfba.home.com>; from hawkes@engr.sgi.com on Mon, Mar 12, 2001 at 04:37:58PM -0800 |
| References: | <004001c0ab55$da882820$6701a8c0@marin1.sfba.home.com> |
| Sender: | owner-linux-origin@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Mon, Mar 12, 2001 at 04:37:58PM -0800, John Hawkes wrote: > Ralf, I've been running my mips64 kernels with KPTBL_PAGE_ORDER bumped > up to 2 (from 1) -- include/asm-mips64/pgtable.h. This doubles the > available vmalloc() space. I imagine it's perfectly okay to use a value > of 4, but I haven't needed to go up that high yet. Please feel free to > make this change in CVS. The question I have is more generic - how much vmalloc space can we expect to be used in worst case in practice on an Origin? Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Fwd: Thanks for Linux on Origin 200, Ralf Baechle |
|---|---|
| Next by Date: | Re: more mips64 vmalloc() space, John Hawkes |
| Previous by Thread: | Fwd: Thanks for Linux on Origin 200, Ralf Baechle |
| Next by Thread: | Re: more mips64 vmalloc() space, John Hawkes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |