Flutterby™! : A Generational Garbage Collection for Processing-in-Memory

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

A Generational Garbage Collection for Processing-in-Memory

2025-07-09 23:46:58.112637+02 by Dan Lyke 0 comments

It has been a long time since I looked at alternate architectures for anything other than cost (eg: embedded), I haven't even done a lot of thinking about massively parallel stuff since my memory of RenderMan's shader language fell out of cache, but I'm finding Gray-in-Young: A Generational Garbage Collection for Processing-in-Memory's description of the UPMEM architecture (now owned by Qualcomm) fascinating.

A 32 bit RISC core with 24 hardware threads dispatched at least 11 cycles apart (which has some interesting saturation/full-utilization implications) with

... a 64-KB scratch pad memory (SPM), a 64-MB DRAM, and a 24-KB instruction memory.

So some really interesting system constraints...

[ related topics: Pixar Robotics Software Engineering Graphics Embedded Devices Architecture ]

comments in ascending chronological order (reverse):

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.