From: "J.A. Magallon" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] i386-arch fixes/enhancements
Date: Fri, 7 Mar 2003 04:11:50 +0100 [thread overview]
Message-ID: <20030307031150.GA19889@werewolf.able.es> (raw)
In-Reply-To: <20030307030858.GA19479@werewolf.able.es>; from jamagallon@able.es on Fri, Mar 07, 2003 at 04:08:58 +0100
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On 03.07 04:08, J.A. Magallon wrote:
> Hi all...
>
> This is set of small patches that allow a finer tuning of i386 arch, and fix a
> small bug:
>
> - 20-x86-p4-prefetch: enables prefetch also for p4. This is a pending bug, IMHO.
> - 21-x86-pII: splits Pentium-II as a separate config option; yes some of us
> still have oldies and would like a slightly better optimized kernel
> - 22-x86-check_gcc: use check_gcc also for Intel CPUs (like others already do)
> to get better gcc flags.
> - 23-x86-mb: implement memory barriers with specific instructions in p3 and p4
> (credits go to Zwane Mwaikambo <zwane@linux.realnet.co.sz>)
>
> Could this ever get into mainline ? Perhaps the only questionable piece is
> the mb changes. How about next -pre ?
>
Ooops. Here they go...
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.21-pre4-jam1 (gcc 3.2.2 (Mandrake Linux 9.1 3.2.2-1mdk))
[-- Attachment #2: 20-x86-p4-prefetch.bz2 --]
[-- Type: application/x-bzip, Size: 360 bytes --]
[-- Attachment #3: 21-x86-pII.bz2 --]
[-- Type: application/x-bzip, Size: 818 bytes --]
[-- Attachment #4: 22-x86-check_gcc.bz2 --]
[-- Type: application/x-bzip, Size: 324 bytes --]
[-- Attachment #5: 23-x86-mb.bz2 --]
[-- Type: application/x-bzip, Size: 826 bytes --]
next prev parent reply other threads:[~2003-03-07 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 3:08 J.A. Magallon
2003-03-07 3:11 ` J.A. Magallon [this message]
2003-03-07 11:12 Margit Schubert-While
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=20030307031150.GA19889@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®