From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 257] Implement demo Load/Store queueing algorithm
Date: Thu, 26 Mar 2020 20:58:58 +0000
Message-ID: <bug-257-13-beUKtcUJue@http.bugs.libre-riscv.org/> (raw)
In-Reply-To: <bug-257-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=257
--- Comment #19 from Jacob Lifshay <programmerjake@gmail.com> ---
I was thinking that the load/store FUs would just split and submit both halves
to a queue-like structure that and the FU would just track both halves
independently until they complete, then merge them. If a load/store doesn't
need to be split, then it would only take one queue entry.
That queue can have all the dependency matrix and scheduling stuff be part of
it and it only needs enough entries to keep the pipeline full -- it doesn't
need double entries to handle split load/stores since the FUs will just stall
if the queue is too full.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 18:40 [libre-riscv-dev] [Bug 257] New: " bugzilla-daemon
2020-03-18 5:23 ` [libre-riscv-dev] [Bug 257] " bugzilla-daemon
2020-03-18 6:59 ` bugzilla-daemon
2020-03-20 11:03 ` bugzilla-daemon
2020-03-20 13:06 ` bugzilla-daemon
2020-03-20 18:34 ` bugzilla-daemon
2020-03-20 19:07 ` bugzilla-daemon
2020-03-20 19:53 ` bugzilla-daemon
2020-03-20 20:21 ` bugzilla-daemon
2020-03-21 0:48 ` bugzilla-daemon
2020-03-21 1:56 ` bugzilla-daemon
2020-03-21 4:12 ` bugzilla-daemon
2020-03-21 15:28 ` bugzilla-daemon
2020-03-21 15:36 ` bugzilla-daemon
2020-03-22 11:37 ` bugzilla-daemon
2020-03-24 11:16 ` bugzilla-daemon
2020-03-24 11:54 ` bugzilla-daemon
2020-03-25 13:07 ` bugzilla-daemon
2020-03-26 17:06 ` bugzilla-daemon
2020-03-26 20:58 ` bugzilla-daemon [this message]
2020-03-26 21:23 ` bugzilla-daemon
[not found] <bug-257-13@https.bugs.libre-soc.org/>
2020-04-22 2:58 ` bugzilla-daemon
2020-04-22 8:30 ` bugzilla-daemon
2020-04-22 8:39 ` bugzilla-daemon
2020-04-22 8:54 ` bugzilla-daemon
2020-04-22 9:48 ` bugzilla-daemon
2020-04-22 13:06 ` bugzilla-daemon
2020-04-22 13:38 ` bugzilla-daemon
2020-04-29 11:16 ` bugzilla-daemon
2020-04-29 21:39 ` bugzilla-daemon
2020-05-06 0:33 ` bugzilla-daemon
2020-05-06 0:36 ` bugzilla-daemon
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=bug-257-13-beUKtcUJue@http.bugs.libre-riscv.org/ \
--to=bugzilla-daemon@libre-riscv.org \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git