From: "Frank Ch. Eigler" <fche@redhat.com>
To: Joseph A <joseph.altmaier@gmail.com>
Cc: cgen@sourceware.org
Subject: Re: how can one achieve pipelined operation?
Date: Wed, 01 Jul 2009 10:50:00 -0000 [thread overview]
Message-ID: <20090701105032.GA13767@redhat.com> (raw)
In-Reply-To: <24210860.post@talk.nabble.com>
Hi -
> I have been working on a port for a while now, and I think everything is
> working except the pipeline. I have tried changing the values of issue and
> done in the functional unit description and I have added a pipeline
> statement to define-model. What do I need to do to achieve pipelined
> operation and/or is there an existing example?
An exposed pipeline is reasonably easily modelled with deferred write
queues in a sid-based simulator; see the mep port.
- FChE
next prev parent reply other threads:[~2009-07-01 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 20:54 Joseph A
2009-07-01 10:50 ` Frank Ch. Eigler [this message]
2009-07-02 3:05 ` Doug Evans
2009-07-02 12:09 ` Dave Korn
2009-07-02 12:29 ` Frank Ch. Eigler
2009-07-02 16:45 ` Joseph A
2009-07-12 2:27 ` Frank Ch. Eigler
2009-07-30 20:12 ` Joseph A
2009-07-30 20:19 ` Frank Ch. Eigler
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=20090701105032.GA13767@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sourceware.org \
--cc=joseph.altmaier@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).