Private
Public Access
ed
212d29c5f1
3-post thread. Replaces the mmap fixed-size log file with a CART file
mmapped on CPU with mapped GPU access (no file IO) + background page
walker to prevent paging out. Beginning of CART is a grid of 32-bit
unsigned values, hex-dumped as the 'log file' to either term or GPU
render. Same framework for CPU and GPU debug ('write and it just
appears'). Visualized as 4-bit/char hex terminal with hex font.
1.2 KiB
1.2 KiB
title, author, handle, post_url, post_id, timestamp, post_count, reply_count, repost_count, like_count, view_count
| title | author | handle | post_url | post_id | timestamp | post_count | reply_count | repost_count | like_count | view_count |
|---|---|---|---|---|---|---|---|---|---|---|
| hits the easy to debug CPU or GPU stuff in the same framework (simply write and | NOTimothyLottes | @NOTimothyLottes | https://x.com/NOTimothyLottes/status/2061124942968545433 | 2061124942968545433 | 2026-05-31 16:37:34 | 3 | 0 | 0 | 2 | 541 |
@NOTimothyLottes — hits the easy to debug CPU or GPU stuff in the same framework (simply write and
Post 1 (2026-05-31 16:32:54)
no-debugger-debug / console / printf-style - prior evolved to one mmapped fixed-width-height log file with an atomic for multi-thread|process messages - but even that seems too complexy ...
Post 2 (2026-05-31 16:35:58) — reply to Post 1
moving to this >>> CART file is mmapped on CPU with mapped GPU access (no file IO) - background page walker to ensure OS won't page it out - beginning of CART file is a grid of 32-bit unsigned values - hex dumping that as my 'log file' - either to term or GPU render
Post 3 (2026-05-31 16:37:34) — reply to Post 2
hits the easy to debug CPU or GPU stuff in the same framework (simply write and it just appears) - it's always a HEX dump, but can show decimal by pretending it's a 4-bit/character terminal with a hex font :)