From: Nigel Stephens <nigel@mips.com>
To: Franck <vagabon.xyz@gmail.com>
Cc: "Kevin D. Kissell" <kevink@mips.com>, linux-mips@linux-mips.org
Subject: Re: [RFC] Optimize swab operations on mips_r2 cpu
Date: Fri, 27 Jan 2006 13:45:51 +0000 [thread overview]
Message-ID: <43DA240F.5070301@mips.com> (raw)
In-Reply-To: <cda58cb80601270103t1419117cq@mail.gmail.com>
Franck wrote:
>2006/1/26, Nigel Stephens <nigel@mips.com>:
>
>
>>You could, but why not stick with -march=4ksd if that's your CPU of
>>choice? It appears to result in marginally smaller code even when using
>>-Os, and should have (slightly) better performance than a generic
>>mips32r2 kernel?
>>
>>
>>
>
>Just to avoid a new CPU_4KSD definition in the kernel code as
>suggested by Kevin. Basically all mips32r2 specific code is the same
>as 4ksd specific code (except the code that deals with SmartMIPS
>extension). So it can use CONFIG_CPU_MIPS32_R2 macro.
>
Not that I'm a Linux hacker, but aren't those separate things? Can't you
compile with -march=4ksd to get the CPU-specific compiler optimisations,
but then use the more generic CONFIG_CPU_MIPSR2 and/or
CONFIG_CPU_SMARTMIPS to select the appropriate code inside the kernel
source (i.e. no need for CONFIG_CPU_4KSD)?
Nigel
next prev parent reply other threads:[~2006-01-27 13:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 9:36 [RFC] Optimize swab operations on mips_r2 cpu Franck
2006-01-25 12:47 ` Ralf Baechle
2006-01-25 13:34 ` Franck
2006-01-25 14:11 ` Kevin D. Kissell
2006-01-25 14:14 ` Ralf Baechle
2006-01-25 14:32 ` Franck
2006-01-25 15:04 ` Ralf Baechle
2006-01-25 18:03 ` Franck
2006-01-25 18:15 ` Kevin D. Kissell
2006-01-26 8:11 ` Franck
2006-01-26 8:26 ` Kevin D. Kissell
2006-01-26 8:47 ` Franck
2006-01-26 9:17 ` Kevin D. Kissell
2006-01-26 9:17 ` Kevin D. Kissell
2006-01-26 11:56 ` Franck
2006-01-26 15:02 ` Franck
2006-01-26 15:23 ` Kevin D. Kissell
2006-01-26 15:23 ` Kevin D. Kissell
2006-01-26 15:29 ` Franck
2006-01-26 15:51 ` Nigel Stephens
2006-01-26 16:31 ` Franck
2006-01-26 16:53 ` Kevin D. Kissell
2006-01-26 16:53 ` Kevin D. Kissell
2006-01-26 16:55 ` Nigel Stephens
2006-01-26 18:02 ` Franck
2006-01-26 20:25 ` Nigel Stephens
2006-01-27 9:03 ` Franck
2006-01-27 10:13 ` Kevin D. Kissell
2006-01-27 10:13 ` Kevin D. Kissell
2006-01-27 10:45 ` Franck
2006-01-27 11:31 ` Ralf Baechle
2006-01-27 12:53 ` Kevin D. Kissell
2006-01-27 12:53 ` Kevin D. Kissell
2006-01-27 14:44 ` Franck
2006-01-27 11:30 ` Ralf Baechle
2006-01-27 13:45 ` Nigel Stephens [this message]
2006-01-27 14:54 ` Franck
2006-01-27 15:04 ` Maciej W. Rozycki
2006-01-27 15:39 ` Kevin D. Kissell
2006-01-27 15:39 ` Kevin D. Kissell
2006-01-27 17:32 ` Franck
2006-01-29 15:07 ` Ralf Baechle
2006-01-30 13:08 ` Maciej W. Rozycki
2006-01-30 14:31 ` Franck
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=43DA240F.5070301@mips.com \
--to=nigel@mips.com \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=vagabon.xyz@gmail.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