From: "Kevin D. Kissell" <kevink@mips.com>
To: "Gilad Benjamini" <yaelgilad@myrealbox.com>, <linux-mips@linux-mips.org>
Subject: Re: lwl-lwr
Date: Tue, 20 May 2003 21:07:26 +0200 [thread overview]
Message-ID: <025401c31f03$0e993370$10eca8c0@grendel> (raw)
In-Reply-To: 1053455551.996c4860yaelgilad@myrealbox.com
> About two months ago there was a discussion
> here about disabling lwl-lwr.
>
> Can someone shed some light on why the discussion
> emerged ?
>
> Is this a performance issue, a processor which
> doesn't support it, or something else ?
>
> If this is a performance issue, I'll be happy
> to hear more details.
I don't remember the discussion in question, but it's a question
which comes up from time to time, due to the existence of
MIPS-like CPUs which lack the (patented) lwl/lwr mechanism
for dealing with unaligned data. The Lexra cores, for example.
There's really no such thing as "disabling" lwl/lwr. They are part
of the base MIPS instruction set. If one wants to live without them,
one can either rig a compiler to emit multi-instruction sequences instead
of lwr/lwl to do the appropriate shifts and masks (which is slower on all
targets), or you can rig the OS to emulate them, and hope that the processors
lacking support will take clean reserved instruction traps, where the function
can be emulated (which is "free" for code running on CPUs with lwl/lwr,
but *really* slow for the guys doing emulation).
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Gilad Benjamini <yaelgilad@myrealbox.com>, linux-mips@linux-mips.org
Subject: Re: lwl-lwr
Date: Tue, 20 May 2003 21:07:26 +0200 [thread overview]
Message-ID: <025401c31f03$0e993370$10eca8c0@grendel> (raw)
Message-ID: <20030520190726.XPAa9vzS90XudYvfXkMxaAIuO3KCG5MvkUF15wkHKDU@z> (raw)
In-Reply-To: 1053455551.996c4860yaelgilad@myrealbox.com
> About two months ago there was a discussion
> here about disabling lwl-lwr.
>
> Can someone shed some light on why the discussion
> emerged ?
>
> Is this a performance issue, a processor which
> doesn't support it, or something else ?
>
> If this is a performance issue, I'll be happy
> to hear more details.
I don't remember the discussion in question, but it's a question
which comes up from time to time, due to the existence of
MIPS-like CPUs which lack the (patented) lwl/lwr mechanism
for dealing with unaligned data. The Lexra cores, for example.
There's really no such thing as "disabling" lwl/lwr. They are part
of the base MIPS instruction set. If one wants to live without them,
one can either rig a compiler to emit multi-instruction sequences instead
of lwr/lwl to do the appropriate shifts and masks (which is slower on all
targets), or you can rig the OS to emulate them, and hope that the processors
lacking support will take clean reserved instruction traps, where the function
can be emulated (which is "free" for code running on CPUs with lwl/lwr,
but *really* slow for the guys doing emulation).
Kevin K.
next prev parent reply other threads:[~2003-05-20 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 18:32 lwl-lwr Gilad Benjamini
2003-05-20 18:34 ` lwl-lwr Will Jhun
2003-05-20 19:07 ` Kevin D. Kissell [this message]
2003-05-20 19:07 ` lwl-lwr Kevin D. Kissell
2003-05-21 0:34 ` lwl-lwr Ralf Baechle
2003-05-21 9:56 ` lwl-lwr Maciej W. Rozycki
2003-05-21 13:40 ` lwl-lwr Kevin D. Kissell
2003-05-21 13:40 ` lwl-lwr Kevin D. Kissell
2003-05-21 12:49 ` lwl-lwr Alan Cox
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='025401c31f03$0e993370$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=yaelgilad@myrealbox.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