From: Ralf Baechle <ralf@linux-mips.org>
To: "Christopher G. Stach II" <cgs@ldsys.net>
Cc: linux-mips@linux-mips.org
Subject: Re: minor patches
Date: Tue, 23 Mar 2004 00:34:40 +0100 [thread overview]
Message-ID: <20040322233440.GA22611@linux-mips.org> (raw)
In-Reply-To: <1079996219.15310.60.camel@localhost>
Leave CONFIG_MAPPED kernel disabled for now; it seems like this option
doesn't deliver the performance benefict it is expected. The reason it's
implemented is primarily because IRIX does the same kernel code
replication and they actually seem to benefit.
Ralf
prev parent reply other threads:[~2004-03-22 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 22:56 minor patches Christopher G. Stach II
2004-03-22 23:34 ` Ralf Baechle [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=20040322233440.GA22611@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=cgs@ldsys.net \
--cc=linux-mips@linux-mips.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