1.9 KiB
title, type, source, source_url, author, handle, post_id, date, archived, draft, tags, description, in_reply_to, parent_post_id
| title | type | source | source_url | author | handle | post_id | date | archived | draft | tags | description | in_reply_to | parent_post_id | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @NOTimothyLottes How about persistent threads? | archive | https://x.com/Colonthreee/status/2121250089377153126 | :3 | Colonthreee | 2121250089377153126 | 2026-11-13 | 2026-11-13 | false |
|
@NOTimothyLottes How about persistent threads? | 2121248962023735367 |
Source
- URL: https://x.com/Colonthreee/status/2121250089377153126
- Author: :3 (@Colonthreee)
- Posted: 2026-11-13 14:33:26
Branch
1/ @Colonthreee ^2121250089377153126
@NOTimothyLottes
How about persistent threads?
2/ @NOTimothyLottes ^2121267632888279464
@Colonthreee
The persistent thread folks like myself and others get constant beat down from the controlling powers, because we like pinned CUs (SMs) and other stuff that doesn't align with the high level vision of the controlling parties.
3/ @Colonthreee ^2121269934944887043
@NOTimothyLottes
That is upfucked. So what can one do? I really like the concept of persistent threadery. ;w;)
4/ @NOTimothyLottes ^2121271929072156976
@Colonthreee
The reality is that we just use it anyway, and people get mad. It was an up-hill battle to do my talk on semi-persistent threads and kernel merging. Many didn't like the idea despite it returning good perf across different chipsets and vendors.
5/ @Colonthreee ^2121279044104978877
@NOTimothyLottes
Oh, where can I see this? OwO
6/ @NOTimothyLottes ^2121290607947899334
@Colonthreee
It might be https://gpuopen.com/learn/presentations/ - gdc 2018 lottes engine optimization hot lap - but I don't have a pptx viewer so I don't have a way to even look at my old talks to find the right one