public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@redhat.com>
To: Paul Miach <paul.miach@edion.com>
Cc: <sid@sources.redhat.com>
Subject: Re: best options for a wide bus?
Date: Thu, 04 Jan 2001 20:20:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.31.0101051515290.18694-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <3A5549AA.6D7DFF4D@edion.com>

Hi Paul,

   I am looking at getting SID to simulate a bus architecture with busses
   wider than 32 bits, ideally busses that are a little over 64 bits wide
   [...]
   - Use multiple 32 bit busses to reach the required width
   - Use "memory" as a pseudo bus
   - Extend the bus object/component to cope with more than 32 bits.

   In terms of performance (simulator time) and ease of implementation,
   what are the trade off in each of the above?

The first two options are easier to implement (since you can do it using
existing facilities).  Both of these options will require twice as many "bus
transactions" as a proper 64+ bit bus.  They also suffer from less obvious
behaviour and, in the case of option 1, will probably limit your component's
usefulness to anyone who doesn't have a similar interface to components they
may wish to connect to yours.

Implementing a proper 64-bit (or greater) bus requires careful
implementation on "smaller" hosts, but since it will be needed sooner or
later for many other components, I believe it's the right way to go.

If you'd like to take a crack at extending the bus class, I'd be glad to
offer any assistance.

Cheers, Ben

  reply	other threads:[~2001-01-04 20:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04 20:10 Paul Miach
2001-01-04 20:20 ` Ben Elliston [this message]
2001-01-05  5:22 ` Frank Ch. Eigler
2001-01-05  5:39   ` Ben Elliston
2001-01-11 21:14 ` matthew green

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=Pine.LNX.4.31.0101051515290.18694-100000@moshpit.cygnus.com \
    --to=bje@redhat.com \
    --cc=paul.miach@edion.com \
    --cc=sid@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).