Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Keith Owens <kaos@ocs.com.au>,
	"'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: Re: DBE table ordering
Date: Fri, 19 Apr 2002 12:28:08 +0400	[thread overview]
Message-ID: <3CBFD518.C413C72A@niisi.msk.ru> (raw)
In-Reply-To: Pine.GSO.3.96.1020418195601.5266A-100000@delta.ds2.pg.gda.pl

Maciej,

"Maciej W. Rozycki" wrote:
> 
> On Thu, 18 Apr 2002, Gleb O. Raiko wrote:
> 
> > I dont't know about other tables and other arches. Perhaps, they need
> > sorting of some tables. But, definetely, sorting isn't required for mips
> > dbe/unaligned access tables.
> 
>  Still it can be done for consistency.  It won't hurt, will it?
> 

Sure, it won't hurt performance. Just looks stupid in this place.

Even if we'll add something like dbe_memcpy, which will require a lot of
addresses in the table in order ot get adequate performance, it'll be
still stupid. And answer your next question, dbe_memcpy is needed for
accesses to busses like VME where Bus{Abort,Error,Fail} are quite legal
and traditionally all of them are traslated to DBE.

Regards,
Gleb.

  reply	other threads:[~2002-04-19  8:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 22:21 DBE table ordering Mark Huang
2002-04-18  3:55 ` Keith Owens
2002-04-18  6:39   ` Mark Huang
2002-04-18  6:39     ` Mark Huang
2002-04-18  6:51     ` Keith Owens
2002-04-18  6:51       ` Keith Owens
2002-04-18  9:37       ` Gleb O. Raiko
2002-04-18  9:49         ` Keith Owens
2002-04-18 12:03           ` Gleb O. Raiko
2002-04-18 17:59             ` Maciej W. Rozycki
2002-04-19  8:28               ` Gleb O. Raiko [this message]
2002-04-19 12:19                 ` Maciej W. Rozycki

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=3CBFD518.C413C72A@niisi.msk.ru \
    --to=raiko@niisi.msk.ru \
    --cc=kaos@ocs.com.au \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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