From: Andrew Morton <akpm@zip.com.au>
To: Paul Larson <plars@austin.ibm.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
William Lee Irwin III <wli@holomorphy.com>,
Dave McCracken <dmccr@us.ibm.com>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH] Optimize out pte_chain take three
Date: Fri, 12 Jul 2002 12:06:29 -0700 [thread overview]
Message-ID: <3D2F28B5.5C7C227D@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0207121323230.13816-100000@eclipse.ltc.austin.ibm.com>
Paul Larson wrote:
>
> I've tried booting this patch on 2.5.25+rmap on an 8-way, with highmem. I
> got a loot of oops on boot (couldn't see the top one because it scrolled
> off the screen) and I havn't had time to set it up with serial console yet
> but I will.
you could stick a `for(;;);' in arch/i386/kernel/traps.c:die() to
stop the scrolling...
I was using Dave's patch for several hours yesterday, no probs.
> Before I do that though I wanted to know if there are any
> known issues with my configuration. I vaguely remember someone mentioning
> problems with multiple swap partitions a while back and that's what I have
>
> /etc/fstab:
> /dev/sda5 swap swap defaults 0 0
> /dev/sda6 swap swap defaults 0 0
> /dev/sda7 swap swap defaults 0 0
> /dev/sda8 swap swap defaults 0 0
> /dev/sda9 swap swap defaults 0 0
> /dev/sda10 swap swap defaults 0 0
> /dev/sda11 swap swap defaults 0 0
> /dev/sda12 swap swap defaults 0 0
>
> for a total of about 15GB swap.
In theory the limits are:
Max of 32 swapdevs
Max of 64G per swapdev.
I normally use two equal-priority disks for swap. Works OK, but I did
considerable futzing in the swap code a while back so some bugs may have
been added.
-
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-07-12 19:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 19:04 [PATCH] Optimize out pte_chain take two Dave McCracken
2002-07-10 0:21 ` Andrew Morton
2002-07-10 14:33 ` [PATCH] Optimize out pte_chain take three Dave McCracken
2002-07-10 15:18 ` Rik van Riel
2002-07-10 17:32 ` William Lee Irwin III
2002-07-10 20:01 ` Andrew Morton
2002-07-10 20:14 ` Rik van Riel
2002-07-10 20:28 ` Andrew Morton
2002-07-10 20:38 ` Rik van Riel
2002-07-13 13:42 ` Daniel Phillips
2002-07-10 20:33 ` Martin J. Bligh
2002-07-10 22:22 ` William Lee Irwin III
2002-07-11 0:39 ` Andrew Morton
2002-07-11 0:47 ` Rik van Riel
2002-07-11 1:27 ` Andrew Morton
2002-07-13 14:10 ` Daniel Phillips
2002-07-11 1:51 ` William Lee Irwin III
2002-07-11 2:28 ` William Lee Irwin III
2002-07-11 19:54 ` Andrew Morton
2002-07-11 20:05 ` Rik van Riel
2002-07-11 20:42 ` Andrew Morton
2002-07-11 20:54 ` Rik van Riel
2002-07-11 21:16 ` Andrew Morton
2002-07-11 21:41 ` Rik van Riel
2002-07-11 22:38 ` Andrew Morton
2002-07-11 23:18 ` Rik van Riel
2002-07-12 18:27 ` Paul Larson
2002-07-12 19:06 ` Andrew Morton [this message]
2002-07-12 19:28 ` Andrew Morton
2002-07-13 15:08 ` Daniel Phillips
2002-07-11 22:54 ` William Lee Irwin III
2002-07-13 14:52 ` Daniel Phillips
2002-07-13 14:08 ` Daniel Phillips
2002-07-13 14:20 ` Daniel Phillips
2002-07-13 14:45 ` Daniel Phillips
2002-07-13 13:22 ` Daniel Phillips
2002-07-13 13:30 ` William Lee Irwin III
2002-07-13 13:55 ` Daniel Phillips
2002-07-13 13:41 ` Daniel Phillips
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=3D2F28B5.5C7C227D@zip.com.au \
--to=akpm@zip.com.au \
--cc=dmccr@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=plars@austin.ibm.com \
--cc=riel@conectiva.com.br \
--cc=wli@holomorphy.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