From: Ralf Baechle <ralf@linux-mips.org>
To: Joseph Chiu <joseph@omnilux.net>
Cc: Pete Popov <ppopov@mvista.com>,
Linux MIPS mailing list <linux-mips@linux-mips.org>
Subject: Re: wired tlb entry?
Date: Wed, 25 Jun 2003 06:59:16 +0200 [thread overview]
Message-ID: <20030625045916.GA28556@linux-mips.org> (raw)
In-Reply-To: <BPEELMGAINDCONKDGDNCMEGADMAA.joseph@omnilux.net>
On Tue, Jun 17, 2003 at 11:51:13AM -0700, Joseph Chiu wrote:
> Michael Guo suggested add_wired_entry -- I'm giving that a try now. I'm
> trying to stick to "the kernel that we trust" (from the perspective here)
> because I'm worried about what I end up breaking trying to take a new
> kernel.
>
> I am behind the time, though, so I'll try to test out 2.4.21-pre4 when I get
> back (I'm not available to run the tests during the rest of this week).
Usual warning - wired entries are almost always a bad idea. TLB entries
are a scarce resource and wiring will reduce the number available for
random replacement even further raising the amount of CPU burned in the
TLB reload handler.
Ralf
next prev parent reply other threads:[~2003-06-25 4:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 0:36 wired tlb entry? Joseph Chiu
2003-06-17 17:18 ` Pete Popov
2003-06-17 18:12 ` Joseph Chiu
2003-06-17 18:16 ` Pete Popov
2003-06-17 18:51 ` Joseph Chiu
2003-06-25 4:59 ` Ralf Baechle [this message]
2003-06-25 18:05 ` Joseph Chiu
2003-06-27 1:02 ` Steven J. Hill
2003-06-27 17:38 ` Joseph Chiu
-- strict thread matches above, loose matches on Subject: below --
2003-06-17 3:28 Guo Michael
2003-06-16 9:32 bootloader problem He Jin
2003-06-16 23:49 ` Wired TLB entry? Joseph Chiu
2003-06-16 23:49 ` Joseph Chiu
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=20030625045916.GA28556@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=joseph@omnilux.net \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@mvista.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 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.