From: Keith M Wesolowski <wesolows@foobazco.org>
To: sparclinux@vger.kernel.org
Subject: Re: [SPARC32] Fix BUG-on-swapout
Date: Tue, 06 Jan 2004 05:24:10 +0000 [thread overview]
Message-ID: <20040106052410.GA13478@foobazco.org> (raw)
In-Reply-To: <20040106040805.GA13026@foobazco.org>
On Mon, Jan 05, 2004 at 11:55:44PM -0500, Pete Zaitcev wrote:
> > -extern struct sparc_phys_banks sp_banks[SPARC_PHYS_BANKS];
> > +extern struct sparc_phys_banks sp_banks[SPARC_PHYS_BANKS+1];
>
> Seems that the first one can be just removed altogether,
> since you're on it.
Yes, you're right. I'll nuke it in my next go-round with mm. Thanks.
> > + KM_PTE2,
>
> Is this needed for anything?
Not at the moment. It is used on other arches for HIGHPTE however.
Thus far I've not dreamed up a sane way to implement that, but a fresh
batch of srmmu mushrooms just came in so I'm optimistic. :-)
The options I've considered:
Uncache-in-place. We can't do large mappings, which wastes memory and
blows TLB locality to hell.
Uncache-in-place for user pagetables, allocate the kernel pagetables
from an uncached block as we do now. This effectively requires user
pagetables in highmem, which not all boxes have.
Abuse the zone allocator to force pagetable allocations to come from
preassigned regions which are either small-mapped (kernel pte) or
unmapped (HIGHPTE for user pagetables). Uncache these in place.
Incredibly evil, needlessly complex, and you can still run out.
The 2.2 way.
Leave it the way it is and put in a less fragmentation-happy
allocator. Sorry, no HIGHPTE.
Please drop your ideas in the suggestion box. Thanks.
--
Keith M Wesolowski <wesolows@foobazco.org> http://foobazco.org/~wesolows
------(( Project Foobazco Coordinator and Network Administrator ))------
"May Buddha bless all stubborn people!"
-- Uliassutai Karakorum Blake
prev parent reply other threads:[~2004-01-06 5:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 4:08 [SPARC32] Fix BUG-on-swapout Keith M Wesolowski
2004-01-06 4:14 ` David S. Miller
2004-01-06 4:55 ` Pete Zaitcev
2004-01-06 5:24 ` Keith M Wesolowski [this message]
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=20040106052410.GA13478@foobazco.org \
--to=wesolows@foobazco.org \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.