<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Short reasons for long vectors in HPC CPUs: a study based on RISC-V · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2309.06865/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2309.06865/feed.xml" rel="self" type="application/rss+xml" /><item><title>Short reasons for long vectors in HPC CPUs: a study based on RISC-V — mentioned by camel-cdr</title><link>https://news.ycombinator.com/item?id=42375494</link><guid isPermaLink="false">urn:hackerpapers:mention:2309.06865:42375494</guid><pubDate>Tue, 10 Dec 2024 10:22:25 GMT</pubDate><description>&lt;p&gt;&amp;quot;Short reasons for long vectors in HPC CPUs: a study based on RISC-V&amp;quot;: https://arxiv.org/abs/2309.06865 Suggests that VLEN&amp;gt;DLEN can help hide the memory latency. &amp;quot;Instruction Scheduling in the Saturn Vector Unit&amp;quot;: https://arxiv.org/html/2412.00997v1 &amp;gt; VII-A Chime Length &amp;gt; The “native” chime length in Saturn, for instructions with no register grouping, is given by the VLEN:DLEN ratio. Increasing the native chime length reduces overall throughput pressure on many components in Saturn, including instruction fetch, load-store queue sizes, issue-queue sizes, and sequencer throughput. &amp;gt; However, a…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2309.06865/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item><item><title>Short reasons for long vectors in HPC CPUs: a study based on RISC-V — mentioned by camel-cdr</title><link>https://news.ycombinator.com/item?id=40476445</link><guid isPermaLink="false">urn:hackerpapers:mention:2309.06865:40476445</guid><pubDate>Sat, 25 May 2024 17:26:27 GMT</pubDate><description>&lt;p&gt;&amp;gt; What is the measurable benefit to implementing 128b SVE2 Probably not much, SVE2 has some nicer instructions, but neon already is quite solid. &amp;gt; And implementing 256b SVE has different issues depending on how you do it For in-order, and not very aggressively out-of-order cores having a larger vector length can be very useful to still get a lot of throughput out of your design. It also helps hide memory latency. Here is a paper: https://ar5iv.labs.arxiv.org/html/2309.06865 and presentation: http://riscv.epcc.ed.ac.uk/assets/files/sc23/Short-reasons-f... For aggressively out-of-order cores it…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2309.06865/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item></channel></rss>
