From: Dan Malek <dan@embeddededge.com>
To: joakim.tjernlund@lumentis.se
Cc: "Linuxppc-Embedded@Lists. Linuxppc. Org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH] Remove 7 instructions in 8xx ITLB Miss when pinned TLBs is set
Date: Sat, 18 Oct 2003 12:55:05 -0400 [thread overview]
Message-ID: <3F917069.6070705@embeddededge.com> (raw)
In-Reply-To: IGEFJKJNHJDCBKALBJLLIEHIGAAA.joakim.tjernlund@lumentis.se
Joakim Tjernlund wrote:
> I realized that kernel space won't cause ITLB misses when CONFIG_PIN_TLB is set. At least on
> my system(no module support).
Why do this? For years we have been trying to remove #ifdefs from the kernel,
this does nothing but add useless configuration complexity, it doesn't save
any space or execution time, and the first time you load a module the kernel
will crash.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-18 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 15:05 [PATCH] Remove 7 instructions in 8xx ITLB Miss when pinned TLBs is set Joakim Tjernlund
2003-10-18 16:55 ` Dan Malek [this message]
[not found] <004001c3967f$f3a7a890$020120b0@jockeXP>
2003-10-20 9:41 ` Joakim Tjernlund
2003-10-20 15:22 ` Dan Malek
2003-10-20 16:54 ` Joakim Tjernlund
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=3F917069.6070705@embeddededge.com \
--to=dan@embeddededge.com \
--cc=joakim.tjernlund@lumentis.se \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).