From: Rusty Trivial Russell <rusty@rustcorp.com.au>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [TRIVIAL] [resend patch] CONFIG_X86_GENERIC description fixup
Date: Mon, 23 Jun 2003 17:19:06 +1000 [thread overview]
Message-ID: <20030623072401.577D62C2E7@lists.samba.org> (raw)
From: Stewart Smith <stewart@linux.org.au>
as per thread on lkml a little while ago, a better explanation
of the X86_GENERIC config option follows. The person who questioned
it originally seemed to like this improved version, so that's one point :)
--- trivial-2.5.73/arch/i386/Kconfig.orig 2003-06-23 17:04:46.000000000 +1000
+++ trivial-2.5.73/arch/i386/Kconfig 2003-06-23 17:04:46.000000000 +1000
@@ -303,9 +303,13 @@
config X86_GENERIC
bool "Generic x86 support"
help
- Including some tuning for non selected x86 CPUs too.
- when it has moderate overhead. This is intended for generic
- distributions kernels.
+ Instead of just including optimizations for the selected
+ x86 variant (e.g. PII, Crusoe or Athlon), include some more
+ generic optimizations as well. This will make the kernel
+ perform better on x86 CPUs other than that selected.
+
+ This is really intended for distributors who need more
+ generic optimizations.
#
# Define implied options from the CPU selection here
--
What is this? http://www.kernel.org/pub/linux/kernel/people/rusty/trivial/
Don't blame me: the Monkey is driving
File: Stewart Smith <stewart@linux.org.au>: [resend patch] CONFIG_X86_GENERIC description fixup
next reply other threads:[~2003-06-23 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 7:19 Rusty Trivial Russell [this message]
2003-06-23 7:56 ` Do we count unstable kernels in use? Damian Wojslaw
2003-07-07 7:57 [TRIVIAL] [resend patch] CONFIG_X86_GENERIC description fixup Rusty Trivial Russell
2003-07-21 11:24 Rusty Trivial Russell
2003-09-04 3:26 Rusty Trivial Russell
2003-09-04 12:20 ` Dave Jones
2003-09-05 0:15 ` Rusty Russell
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=20030623072401.577D62C2E7@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
Powered by JetHome