Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > sci.physics.relativity > #671475 > unrolled thread

I'm a spinner, I'm a sinner [Dmitry Vyukov for pi-WAM] (Was: Paul Tarau versus Mr. Taskmanager, who would win? [A PDP-11 Humunkulus from 1979])

Back to article view | Back to sci.physics.relativity

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  I'm a spinner, I'm a sinner [Dmitry Vyukov for pi-WAM] (Was: Paul Tarau versus Mr. Taskmanager, who would win? [A PDP-11 Humunkulus from 1979]) Mild Shock <janburse@fastmail.fm> - 2026-07-19 11:53 +0200
    Corr.: Re: I'm a spinner, I'm a sinner [Dmitry Vyukov for pi-WAM] (Was: Paul Tarau versus Mr. Taskmanager, who would win? [A PDP-11 Humunkulus from 1979]) Mild Shock <janburse@fastmail.fm> - 2026-07-19 11:55 +0200
    Re: I'm a spinner, I'm a sinner [Dmitry Vyukov for pi-WAM] (Was: Paul Tarau versus Mr. Taskmanager, who would win? [A PDP-11 Humunkulus from 1979]) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-19 14:04 -0700
      Re: I'm a spinner, I'm a sinner [Dmitry Vyukov for pi-WAM] (Was: Paul Tarau versus Mr. Taskmanager, who would win? [A PDP-11 Humunkulus from 1979]) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-19 14:07 -0700
        Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov (Was: I'm a spinner, I'm a sinner [Dmitry Vyukov for pi-WAM]) Mild Shock <janburse@fastmail.fm> - 2026-07-20 08:31 +0200
          Re: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov (Was: I'm a spinner, I'm a sinner [Dmitry Vyukov for pi-WAM]) Romelio Balakhonsky <lrel@lao.ru> - 2026-07-20 10:07 +0000
            The Cache Identity Crisis by Micro Penis (Re: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov) Mild Shock <janburse@fastmail.fm> - 2026-07-20 13:51 +0200
              Just RTFM the RDNA 3.5 specs! [GPU Cache Lines] (Was: The Cache Identity Crisis by Micro Penis) Mild Shock <janburse@fastmail.fm> - 2026-07-20 14:09 +0200
                The large memory tax: ECC RAM (Was: Just RTFM the RDNA 3.5 specs! [GPU Cache Lines]) Mild Shock <janburse@fastmail.fm> - 2026-07-20 14:22 +0200
                Friendly Reminder: GPU 10x more performant than CPU (Re: Just RTFM the RDNA 3.5 specs! [GPU Cache Lines]) Mild Shock <janburse@fastmail.fm> - 2026-07-21 00:40 +0200
                  Breaking the CUDA edge in AI by WebGPU (Re: Friendly Reminder: GPU 10x more performant than CPU) Mild Shock <janburse@fastmail.fm> - 2026-07-21 00:57 +0200
                    Like WebAssembly before it, WebGPU has "escaped" the browser. (Re: Breaking the CUDA edge in AI by WebGPU (Re: Friendly Reminder: GPU 10x more performant than CPU) Mild Shock <janburse@fastmail.fm> - 2026-07-21 01:07 +0200
                    Re: Breaking the CUDA edge in AI by WebGPU (Re: Friendly Reminder: GPU 10x more performant than CPU) Will Bakshandaev <bev@lwesi.ru> - 2026-07-21 14:33 +0000
                      http://localhost:567921/ is a private REST endpoint [Teaching Micro Penis Vilage Idiot] (Was: Breaking the CUDA edge in AI by WebGPU) Mild Shock <janburse@fastmail.fm> - 2026-07-21 22:41 +0200
                        If you are paranoid you can use Falco [Agentic AI] (Re: http://localhost:567921/ is a private REST endpoint) Mild Shock <janburse@fastmail.fm> - 2026-07-21 22:57 +0200
                          What would an EMACs guru say [Windows Recall] (Was: If you are paranoid you can use Falco [Agentic AI]) Mild Shock <janburse@fastmail.fm> - 2026-07-21 23:33 +0200
                        Re: http://localhost:567921/ is a private REST endpoint [Teaching Micro Penis Vilage Idiot] (Was: Breaking the CUDA edge in AI by WebGPU) Hants Baibikov <vi@bi.ru> - 2026-07-21 21:51 +0000
                        Re: http://localhost:567921/ is a private REST endpoint [Teaching Micro Penis Vilage Idiot] (Was: Breaking the CUDA edge in AI by WebGPU) Pascual Talbaev <ps@laalapa.ru> - 2026-07-21 22:02 +0000
                        Decide what you critique tiny winy penis (Was: http://localhost:567921/ is a private REST endpoint) Mild Shock <janburse@fastmail.fm> - 2026-07-22 08:13 +0200
                          How confused is tiny winy penis? (Re: Decide what you critique tiny winy penis) Mild Shock <janburse@fastmail.fm> - 2026-07-22 08:29 +0200
                            Maybe change your hobby, become a dog owner? (Re: How confused is tiny winy penis?) Mild Shock <janburse@fastmail.fm> - 2026-07-22 09:38 +0200
                          Re: Decide what you critique tiny winy penis (Was: http://localhost:567921/ is a private REST endpoint) Audie Balaban <aie@ndabl.ru> - 2026-07-22 08:02 +0000
                            Even dogs know Switzerland != Germany [Syphilis Brain Micro Penis] (Re: Decide what you critique tiny winy penis (Was: http://localhost:567921/ is a private REST endpoint) Mild Shock <janburse@fastmail.fm> - 2026-07-22 11:17 +0200
                              Re: Even dogs know Switzerland != Germany [Syphilis Brain Micro Penis] (Re: Decide what you critique tiny winy penis (Was: http://localhost:567921/ is a private REST endpoint) Roque Bahtinov <aoqhi@hrot.ru> - 2026-07-22 12:04 +0000
                                My Swift Go 16 AI has no IMEI, are you nuts? (Was: Even dogs know Switzerland != Germany [Syphilis Brain Micro Penis]) Mild Shock <janburse@fastmail.fm> - 2026-07-22 14:12 +0200
                                  Same nickname and email, could post faster [5 year old moron] (Re: My Swift Go 16 AI has no IMEI, are you nuts?) Mild Shock <janburse@fastmail.fm> - 2026-07-22 14:24 +0200
              Re: The Cache Identity Crisis by Micro Penis (Re: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov) Jeiker Makulov <rmkru@eeeamu.ru> - 2026-07-20 16:18 +0000
                L1,..,Ln caches are located on the CPU AND on the GPU (Was: The Cache Identity Crisis by Micro Penis) Mild Shock <janburse@fastmail.fm> - 2026-07-20 19:33 +0200
                  GPU Cache Hierarchy: Understanding L1, L2, and VRAM (Re: L1,..,Ln caches are located on the CPU AND on the GPU) Mild Shock <janburse@fastmail.fm> - 2026-07-20 19:42 +0200
                    Re: GPU Cache Hierarchy: Understanding L1, L2, and VRAM (Re: L1,..,Ln caches are located on the CPU AND on the GPU) Zackee Mulatov <azauv@omtla.ru> - 2026-07-20 19:09 +0000
                      Well thats good, co-location, onto the same processor die (Was: GPU Cache Hierarchy: Understanding L1, L2, and VRAM) Mild Shock <janburse@fastmail.fm> - 2026-07-20 22:02 +0200
                        Where is micro penis mental error? (Re: Well thats good, co-location, onto the same processor die) Mild Shock <janburse@fastmail.fm> - 2026-07-20 22:07 +0200
                        Re: Well thats good, co-location, onto the same processor die (Was: GPU Cache Hierarchy: Understanding L1, L2, and VRAM) Hermis Molochkov <me@olech.ru> - 2026-07-20 22:27 +0000
          Re: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov (Was: I'm a spinner, I'm a sinner [Dmitry Vyukov for pi-WAM]) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-20 13:40 -0700
            I didn't find Futex in WebGPU / WGSL (Was: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov) Mild Shock <janburse@fastmail.fm> - 2026-07-20 23:25 +0200
              Re: I didn't find Futex in WebGPU / WGSL (Was: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-20 14:32 -0700
                Re: I didn't find Futex in WebGPU / WGSL (Was: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-20 14:35 -0700
                  There is no imageAtomicAdd in WGSL (Was: I didn't find Futex in WebGPU / WGSL) Mild Shock <janburse@fastmail.fm> - 2026-07-21 00:12 +0200
                    OpenGL is dead. Apple said bye bye / Wayland Compositor (Was: There is no imageAtomicAdd in WGSL) Mild Shock <janburse@fastmail.fm> - 2026-07-21 00:24 +0200
                    Re: There is no imageAtomicAdd in WGSL (Was: I didn't find Futex in WebGPU / WGSL) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-20 16:15 -0700
                      Flogging a Dead Horse, OpenGL is EOL (Was: There is no imageAtomicAdd in WGSL) Mild Shock <janburse@fastmail.fm> - 2026-07-21 01:24 +0200
                        imageAtomicAdd trivial, Dmitry Vyukov requires capacity (Re: Flogging a Dead Horse, OpenGL is EOL (Was: There is no imageAtomicAdd in WGSL) Mild Shock <janburse@fastmail.fm> - 2026-07-21 01:32 +0200
                          capacity = 2^n for some n / systolic system (Was: imageAtomicAdd trivial, Dmitry Vyukov requires capacity) Mild Shock <janburse@fastmail.fm> - 2026-07-21 01:37 +0200
                            Source of the benchmark for DmitryVyukov (Re: capacity = 2^n for some n / systolic system) Mild Shock <janburse@fastmail.fm> - 2026-07-21 01:45 +0200
                          Re: imageAtomicAdd trivial, Dmitry Vyukov requires capacity (Re: Flogging a Dead Horse, OpenGL is EOL (Was: There is no imageAtomicAdd in WGSL) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-07-20 17:00 -0700
                            I never used OpenGL Version 4.2 and later (Re: imageAtomicAdd trivial, Dmitry Vyukov requires capacity) Mild Shock <janburse@fastmail.fm> - 2026-07-21 08:49 +0200
                              Because of MIMD you have to reassess algorithms (Was: I never used OpenGL Version 4.2 and later) Mild Shock <janburse@fastmail.fm> - 2026-07-21 08:59 +0200
                                Why MIMD is interesting for pi-WAM? Mild Shock <janburse@fastmail.fm> - 2026-07-21 09:16 +0200
                                  Re: Why MIMD is interesting for pi-WAM? Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-07-21 00:32 -0700
                                Re: Because of MIMD you have to reassess algorithms (Was: I never used OpenGL Version 4.2 and later) Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-07-21 00:42 -0700
                                  You still don't understand "budget" [Rossy Boy slower than Micro Penis] (Was: Because of MIMD you have to reassess algorithms) Mild Shock <janburse@fastmail.fm> - 2026-07-21 10:13 +0200
                                    Go on Rossy Boy, ask more stupid questions (Was: You still don't understand "budget" [Rossy Boy slower than Micro Penis]) Mild Shock <janburse@fastmail.fm> - 2026-07-21 10:17 +0200
                                      Need to be Einstein to understand Giga Lips (Was: Go on Rossy Boy, ask more stupid questions) Mild Shock <janburse@fastmail.fm> - 2026-07-21 10:22 +0200
                                        Marketing invents Gucci Bag AI Laptops (Was: Need to be Einstein to understand Giga Lips) Mild Shock <janburse@fastmail.fm> - 2026-07-21 10:43 +0200
                                      Re: Go on Rossy Boy, ask more stupid questions (Was: You still don't understand "budget" [Rossy Boy slower than Micro Penis]) Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-07-21 08:59 -0700
                                        Rossy Boy says I am a crazy frothing lunatic (Was: Go on Rossy Boy, ask more stupid questions) Mild Shock <janburse@fastmail.fm> - 2026-07-21 22:27 +0200
                                          Re: Rossy Boy says I am a crazy frothing lunatic (Was: Go on Rossy Boy, ask more stupid questions) Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-07-21 13:52 -0700

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#671547 — Maybe change your hobby, become a dog owner? (Re: How confused is tiny winy penis?)

Hey Micro Penis,

Maybe change your hobby, become a dog owner?
Instead of fiddling with your Sputnik Commodore
C64 from 1982, modded to run on a 8088.

Maybe change your hobby, become a dog owner.
But watch out, its not as easy as GitHub diploma,
you cannot carry a hackathon certificate home

by showing up 3 days and let your team mates
do all the pitch presentations and pretend
hacking. The hurdles here are quite high:

"Becoming a dog owner involves both a rewarding
commitment and legal obligations. Under law,
you must complete an accredited practical dog

education course within one year of acquiring
your pet. You must also register your dog with
the national AMICUS Database, have a veterinarian

implant a microchip, and pay the annual cantonal dog tax."

Good luck, get a life!

Bye

Mild Shock schrieb:
> Hi,
> 
> How confused is tiny winy penis?
> For the 100th time the budget here:
> 
> 11.4 Giga Lips with a Budget Laptop
> Ryzen AI 7 350 w/ Radeon 860M
> https://github.com/Jean-Luc-Picard-2021/gigabudget
> 
> is a laptop and not a smartphone. It
> has no cellphone number. And w/ means
> integrated GPU on the silicon chip,
> 
> and not a GPU connected to the mainboard
> via some PCI bus. The model is a acer
> swift go, I already posted this info:
> 
> Swift Go 16 AI SFG16-61-R21J Notebook
> https://www.acer.com/ch-de/laptops/swift/swift-go-16-ai-amd/pdp/NX.JCREZ.007 
> 
> 
> Bye
> 
> Mild Shock schrieb:
>> Hi,
>>
>> Maybe you could post some subtantial critique moron?
>> Instead of gibberish all the time. What does a cellphone
>> number have to do with a REST endpoint? Nothing!
>>
>> Its all locally and my laptop has no cellphone number:
>>
>> Start the REST API server
>>
>> To start the server, run the following command:
>> lms server start
>>
>> Endpoints
>>
>> GET /api/v0/models
>> List all loaded and downloaded models
>> Example request
>> curl -H "Authorization: Bearer $LM_API_TOKEN" 
>> http://localhost:1234/api/v0/models
>> Response format
>> {
>>    "object": "list",
>>    "data": [
>>      {
>>        "id": "qwen2-vl-7b-instruct",
>>        "object": "model",
>>        "type": "vlm",
>>        "publisher": "mlx-community",
>>        "arch": "qwen2_vl"
>> Etc...
>> https://lmstudio.ai/docs/developer/rest/endpoints
>>
>> Bye
>>
>> BTW: LM Studio recently introduced LM Link,
>> which provides some VPN. It can be used to
>> create clients or servers that run models.
>>
>> It is end-to-end encrypted, and built on top
>> of custom Tailscale mesh VPNs. This is for
>> the paranoid, that want to acccess a
>>
>> LLM from one end of the globe, that sits
>> on the other end of the globe, and have
>> no evesdroper or whatever on the
>>
>> information that is exchanged.
>>
>>> Mild Shock wrote:
>>>
>>>> http://localhost:567921/ is private you moron.,
>>>> or what ever port REST is using. You typically access an offline AI 
>>>> assistant, via some REST end-point
>>>
>>> yet one more proof this half german inbreed is an imbecile, ports go 
>>> up to 16bits/64k only, idiot, you cant have a localhost: whatever 
>>> wrong number you put there. You extreme fucking idiot. 
>>
>>>> on your machine. Nothing to do with Google Chrome browser security. 
>>>> You can make it as private as you want, by having a firewall and not 
>>>> outward
>>>> or inward
>>>
>>> yes, i can see your point, they just want your private cellphone 
>>> number, there rest is private and free, idiot
>>
>>
>>
>> Mild Shock schrieb:
>>> Hi,
>>>
>>> ------------------- begin --------------------
>>> Teaching Micro Penis Vilage Idiot
>>> ------------------- begin --------------------
>>>
>>> You dont have to use WebLLM, respectively
>>> WebGPU / WGSL literally, just read the next
>>> post I did AND use your brains moron:
>>>
>>> Like WebAssembly before it, WebGPU has "escaped" the browser
>>> https://blog.4dpipeline.com/client-side-ai-is-here-how-webgpu-transforms-your-gpu-server-economics 
>>>
>>>
>>> http://localhost:567921/ is private you moron.,
>>> or what ever port REST is using. You typically access
>>> an offline AI assistant, via some REST end-point
>>>
>>> on your machine. Nothing to do with Google Chrome
>>> browser security. You can make it as private as you want, by
>>> having a firewall and not outward or inward
>>>
>>> connection at all, only your REST end-point
>>> on your machine. Or if you want a REST end-point
>>> on a server of yours in the same intranet.
>>>
>>> You don't need to use the internet, or put
>>> something on the extranet, or use some sort of
>>> subscription. What you need is access through
>>>
>>> the firewall to download the REST software
>>> and the LLM model. Tools like LM Studio and oMLX
>>> offer this download and also install REST endpoint.
>>>
>>> ------------------- end --------------------
>>> Teaching Micro Penis Vilage Idiot}
>>> ------------------- end --------------------
>>>
>>> Bye
>>>
>>> Will Bakshandaev schrieb:
>>>> Mild Shock wrote:
>>>>
>>>>> Frameworks like WebLLM leverage WebGPU to run large language models
>>>>> locally inside browsers like Google Chrome, providing completely
>>>>> private, offline AI assistants.
>>>>
>>>> since when google chrome private, think again
>>>>
>>>
>>
> 

[toc] | [prev] | [next] | [standalone]

#671549 — Re: Decide what you critique tiny winy penis (Was: http://localhost:567921/ is a private REST endpoint)

Mild Shock wrote:

> Maybe you could post some subtantial critique moron? Instead of
> gibberish all the time. What does a cellphone number have to do with a
> REST endpoint? Nothing!
> 
> Its all locally and my laptop has no cellphone number:

you lying bitch, your arse is burning, you said google chrome security, 
and gave them your cellphone number, fucking idiot. And you put wrong 
ports numbers along the localhost: idiot

[toc] | [prev] | [next] | [standalone]

#671550 — Even dogs know Switzerland != Germany [Syphilis Brain Micro Penis] (Re: Decide what you critique tiny winy penis (Was: http://localhost:567921/ is a private REST endpoint)

Hi,

Moron, from St. Petersburg, with only 5G internet.
You confuse browser security model with Google account.
No cellphone number involved in a brower JavaScript

secure sand box, for executing JavaScript in the main
and in isolated silod workers. Also you seem not to see
that I post CHF price tags and CHF product listings.

So what makes you think Switzerland == Germany,
when you rant like below. Even a dog knows that a
non-EU country cannot be the same as EU country:

> you stupid half german, the comparisons along 
> memories arrays gpu card located, are taking place 
> parallel without cpu intervention, you fucking 
> illiterate idiot. You soon will become a quarter 
> german hence 3/4 russian old days, historically. It's coming
 >
 > German energy crisis caused by ‘lack of Russian gas’ – Merz
 > https://www.rt.com/news/643254-germany-crisis-russian-gas/

Bye

P.S.: EU = European Union

Audie Balaban schrieb:
> Mild Shock wrote:
> 
>> Maybe you could post some subtantial critique moron? Instead of
>> gibberish all the time. What does a cellphone number have to do with a
>> REST endpoint? Nothing!
>>
>> Its all locally and my laptop has no cellphone number:
> 
> you lying bitch, your arse is burning, you said google chrome security,
> and gave them your cellphone number, fucking idiot. And you put wrong
> ports numbers along the localhost: idiot
> 

[toc] | [prev] | [next] | [standalone]

#671556 — Re: Even dogs know Switzerland != Germany [Syphilis Brain Micro Penis] (Re: Decide what you critique tiny winy penis (Was: http://localhost:567921/ is a private REST endpoint)

Mild Shock wrote:

> Moron, from St. Petersburg, with only 5G internet.
> You confuse browser security model with Google account.
> No cellphone number involved in a brower JavaScript

cretin, they already have your phone number, the IMEI, email adr, location 
and everything, your friends included. Idiot, I cant even believe it.

[toc] | [prev] | [next] | [standalone]

#671557 — My Swift Go 16 AI has no IMEI, are you nuts? (Was: Even dogs know Switzerland != Germany [Syphilis Brain Micro Penis])

Hi,

Die IMEI (International Mobile Equipment Identity)
ist eine 15-stellige, weltweit eindeutige Seriennummer,
die jedes Mobiltelefon identifiziert.

Die meisten Laptops haben keine IMEI-Nummer. Sie
existiert nur, wenn das Gerät über ein integriertes
Mobilfunkmodem (WWAN/LTE/5G-Karte) für SIM-Karten verfügt.

Also in Switzerland people have fiber optic earth
cables for internet, and not some 5G over the air.
I got like 10 GBit/s fiber here in my home.

There are 96 internet service providers that offer that speed:

https://www.comparis.ch/telecom/zuhause/angebote/list?requestobject={%22products%22%3A[1]%2C%22onlyOffersWithoutMinimumDuration%22%3Afalse%2C%22internetSpeedTypes%22%3A[1]%2C%22connectionTypes%22%3A[1]%2C%22tvOptions%22%3A[]%2C%22landlineOptions%22%3A[]%2C%22providers%22%3A[]%2C%22showDiscountedOnly%22%3Afalse%2C%22addressCheckInfo%22%3A{%22AvailableCableProviders%22%3Anull%2C%22AvailableVdslSpeed%22%3Anull%2C%22AvailableFiberSpeed%22%3Anull%2C%22AvailableInit7Fiber%22%3Afalse%2C%22AvailableAllFiberProvidersExceptInit7%22%3Afalse}%2C%22address%22%3A{%22Zip%22%3Anull%2C%22Street%22%3Anull%2C%22StreetNumber%22%3Anull}}
Angebote für Internet, TV und Festnetz-Telefon, sowie Kombiangebote

Its handy to download LLMs which have GB sizes.

But this laptop has no SIM Card, even not a e-SIM:

> How confused is tiny winy penis?
> For the 100th time the budget here:
> 
> 11.4 Giga Lips with a Budget Laptop
> Ryzen AI 7 350 w/ Radeon 860M
> https://github.com/Jean-Luc-Picard-2021/gigabudget
> 
> is a laptop and not a smartphone. It
> has no cellphone number. And w/ means
> integrated GPU on the silicon chip,
> 
> and not a GPU connected to the mainboard
> via some PCI bus. The model is a acer
> swift go, I already posted this info:
> 
> Swift Go 16 AI SFG16-61-R21J Notebook
> https://www.acer.com/ch-de/laptops/swift/swift-go-16-ai-amd/pdp/NX.JCREZ.007

Bye

Roque Bahtinov schrieb:
> Mild Shock wrote:
> 
>> Moron, from St. Petersburg, with only 5G internet.
>> You confuse browser security model with Google account.
>> No cellphone number involved in a brower JavaScript
> 
> cretin, they already have your phone number, the IMEI, email adr, location
> and everything, your friends included. Idiot, I cant even believe it.
> 

[toc] | [prev] | [next] | [standalone]

#671558 — Same nickname and email, could post faster [5 year old moron] (Re: My Swift Go 16 AI has no IMEI, are you nuts?)

Hi,

5 year old moron. Why does it take 11 hours until
your next nonsense pours in? Takes too much time
to create a new nickname and new email every time?

Well once a moron, always a moron.

Bye

Mild Shock schrieb:
> Hi,
> 
> Die IMEI (International Mobile Equipment Identity)
> ist eine 15-stellige, weltweit eindeutige Seriennummer,
> die jedes Mobiltelefon identifiziert.
> 
> Die meisten Laptops haben keine IMEI-Nummer. Sie
> existiert nur, wenn das Gerät über ein integriertes
> Mobilfunkmodem (WWAN/LTE/5G-Karte) für SIM-Karten verfügt.
> 
> Also in Switzerland people have fiber optic earth
> cables for internet, and not some 5G over the air.
> I got like 10 GBit/s fiber here in my home.
> 
> There are 96 internet service providers that offer that speed:
> 
> https://www.comparis.ch/telecom/zuhause/angebote/list?requestobject={%22products%22%3A[1]%2C%22onlyOffersWithoutMinimumDuration%22%3Afalse%2C%22internetSpeedTypes%22%3A[1]%2C%22connectionTypes%22%3A[1]%2C%22tvOptions%22%3A[]%2C%22landlineOptions%22%3A[]%2C%22providers%22%3A[]%2C%22showDiscountedOnly%22%3Afalse%2C%22addressCheckInfo%22%3A{%22AvailableCableProviders%22%3Anull%2C%22AvailableVdslSpeed%22%3Anull%2C%22AvailableFiberSpeed%22%3Anull%2C%22AvailableInit7Fiber%22%3Afalse%2C%22AvailableAllFiberProvidersExceptInit7%22%3Afalse}%2C%22address%22%3A{%22Zip%22%3Anull%2C%22Street%22%3Anull%2C%22StreetNumber%22%3Anull}} 
> 
> Angebote für Internet, TV und Festnetz-Telefon, sowie Kombiangebote
> 
> Its handy to download LLMs which have GB sizes.
> 
> But this laptop has no SIM Card, even not a e-SIM:
> 
>> How confused is tiny winy penis?
>> For the 100th time the budget here:
>>
>> 11.4 Giga Lips with a Budget Laptop
>> Ryzen AI 7 350 w/ Radeon 860M
>> https://github.com/Jean-Luc-Picard-2021/gigabudget
>>
>> is a laptop and not a smartphone. It
>> has no cellphone number. And w/ means
>> integrated GPU on the silicon chip,
>>
>> and not a GPU connected to the mainboard
>> via some PCI bus. The model is a acer
>> swift go, I already posted this info:
>>
>> Swift Go 16 AI SFG16-61-R21J Notebook
>> https://www.acer.com/ch-de/laptops/swift/swift-go-16-ai-amd/pdp/NX.JCREZ.007 
>>
> 
> Bye
> 
> Roque Bahtinov schrieb:
>> Mild Shock wrote:
>>
>>> Moron, from St. Petersburg, with only 5G internet.
>>> You confuse browser security model with Google account.
>>> No cellphone number involved in a brower JavaScript
>>
>> cretin, they already have your phone number, the IMEI, email adr, 
>> location
>> and everything, your friends included. Idiot, I cant even believe it.
>>
> 

[toc] | [prev] | [next] | [standalone]

#671500 — Re: The Cache Identity Crisis by Micro Penis (Re: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov)

Mild Shock wrote:

> Yes of course, Micro Penis will know. Nothing, LoL But here we find how
> village idiot Micro Penis is.
> The Cache Identity Crisis by Micro Penis:
> 
> Claiming that L1/L2/L3 caches and core topology are "embedded cpu
> registers area,
> it has nothing to do with the ram." That is a brilliant piece of
> hardware fiction.
> 
> Caches are SRAM acting as a hierarchical

imbecile, formatting code like that puts you in prison in normal 
countries. You are using entire lines for single chars, ie  "}" etc, 
imbecile.

also, fucking lying illiterate imbecile

L1, L2, and L3 caches are located on the CPU, not in the system RAM. They 
form a high-speed memory hierarchy embedded directly within or immediately 
adjacent to the processor cores to minimize data access latency. 

[toc] | [prev] | [next] | [standalone]

#671501 — L1,..,Ln caches are located on the CPU AND on the GPU (Was: The Cache Identity Crisis by Micro Penis)

Hi,

You are a moron right? Modern GPU has its
own L1,..,Ln caches. RTFM ASAP you brain
amputated vodka alcoholic.

Russian Hardbass - Crazy Dance
https://www.youtube.com/watch?v=6OoglRuT0jY

Bye

Jeiker Makulov schrieb:
> Mild Shock wrote:
> 
>> Yes of course, Micro Penis will know. Nothing, LoL But here we find how
>> village idiot Micro Penis is.
>> The Cache Identity Crisis by Micro Penis:
>>
>> Claiming that L1/L2/L3 caches and core topology are "embedded cpu
>> registers area,
>> it has nothing to do with the ram." That is a brilliant piece of
>> hardware fiction.
>>
>> Caches are SRAM acting as a hierarchical
> 
> imbecile, formatting code like that puts you in prison in normal
> countries. You are using entire lines for single chars, ie  "}" etc,
> imbecile.
> 
> also, fucking lying illiterate imbecile
> 
> L1, L2, and L3 caches are located on the CPU, not in the system RAM. They
> form a high-speed memory hierarchy embedded directly within or immediately
> adjacent to the processor cores to minimize data access latency.
> 

[toc] | [prev] | [next] | [standalone]

#671502 — GPU Cache Hierarchy: Understanding L1, L2, and VRAM (Re: L1,..,Ln caches are located on the CPU AND on the GPU)

Hi,

Just read something for once you alcoholic:

GPU Cache Hierarchy: Understanding L1, L2, and VRAM
https://charlesgrassi.dev/blog/gpu-cache-hierarchy/

Measuring Cache Efficiency

GPU profilers like NVIDIA Nsight, AMD Radeon
GPU Profiler, and RenderDoc expose cache hit
rates and memory throughput. Key metrics to watch:

- L1 Hit Rate: Should be >80% for well-optimized
     shaders. Below 60% indicates access pattern problems.
- L2 Hit Rate: Measures working set fit.
     Below 70% suggests texture thrashing or too many unique textures.
- Texture Memory Throughput: Compare to theoretical
     max. Low throughput with high latency = cache misses.
- Memory-bound vs Compute-bound: If memory is the
     bottleneck, cache optimization has highest impact.

If the GPU is a discrete GPU, it has VRAM,
If the GPU is an accelerator processing unit (APU),
it shares the system memory with the CPU.

In the APU scenrio often advanced unified memory
is used, which can be multi channel for example.
The high L1 and L2 hit rate for shaders, translates

also to pi-WAM. Which shows, in the example I used,
a quite good GPU saturation, less memory bound and
more compute bound. I have compute these figures already.

Bye

Mild Shock schrieb:
> Hi,
> 
> You are a moron right? Modern GPU has its
> own L1,..,Ln caches. RTFM ASAP you brain
> amputated vodka alcoholic.
> 
> Russian Hardbass - Crazy Dance
> https://www.youtube.com/watch?v=6OoglRuT0jY
> 
> Bye
> 
> Jeiker Makulov schrieb:
>> Mild Shock wrote:
>>
>>> Yes of course, Micro Penis will know. Nothing, LoL But here we find how
>>> village idiot Micro Penis is.
>>> The Cache Identity Crisis by Micro Penis:
>>>
>>> Claiming that L1/L2/L3 caches and core topology are "embedded cpu
>>> registers area,
>>> it has nothing to do with the ram." That is a brilliant piece of
>>> hardware fiction.
>>>
>>> Caches are SRAM acting as a hierarchical
>>
>> imbecile, formatting code like that puts you in prison in normal
>> countries. You are using entire lines for single chars, ie  "}" etc,
>> imbecile.
>>
>> also, fucking lying illiterate imbecile
>>
>> L1, L2, and L3 caches are located on the CPU, not in the system RAM. They
>> form a high-speed memory hierarchy embedded directly within or 
>> immediately
>> adjacent to the processor cores to minimize data access latency.
>>
> 

[toc] | [prev] | [next] | [standalone]

#671505 — Re: GPU Cache Hierarchy: Understanding L1, L2, and VRAM (Re: L1,..,Ln caches are located on the CPU AND on the GPU)

Mild Shock wrote:

> Just read something for once you alcoholic:
> 
> GPU Cache Hierarchy: Understanding L1, L2, and VRAM
> https://charlesgrassi.dev/blog/gpu-cache-hierarchy/
> 
> Measuring Cache Efficiency
> 
> GPU profilers like NVIDIA Nsight, AMD Radeon GPU Profiler, and RenderDoc
> expose cache hit rates and memory throughput. Key metrics to watch:

nothing. That's too located close to the same cpu, idiot. It has nothing 
to do with anything. This cretin dontt undrestand what a cache is. He 
thinks it's ram.

[toc] | [prev] | [next] | [standalone]

#671506 — Well thats good, co-location, onto the same processor die (Was: GPU Cache Hierarchy: Understanding L1, L2, and VRAM)

Hi,

 > That's too located close to the same cpu, idiot.

Yes, colocating a CPU and GPU onto the same
processor die or package provides massive b
enefits, primarily by eliminating the latency
and bandwidth bottlenecks of moving data
across a motherboard.

Individual L1 Caches: Yes, the CPU cores and
the GPU compute units (Streaming Multiprocessors /
Compute Units) still maintain private,
individual L1 caches.

The "Colocation" Benefit: In traditional
setups (a separate CPU and GPU on PCIe slots),
data must be copied from system RAM to the
GPU's VRAM. When a CPU and GPU are colocated
(like in Apple Silicon, AMD APUs, or Intel
processors), they share a Unified Memory
Architecture (UMA). Both processors can read
and write to the exact same physical memory
pool without redundant data copying

Shared Last-Level Cache: While the L1 caches
remain separate, colocated architectures
often share a high-capacity Last-Level
Cache (L2 or L3). This allows the CPU and
GPU to quickly pass data back and forth
locally on the chip.

Bye

Zackee Mulatov schrieb:
> Mild Shock wrote:
> 
>> Just read something for once you alcoholic:
>>
>> GPU Cache Hierarchy: Understanding L1, L2, and VRAM
>> https://charlesgrassi.dev/blog/gpu-cache-hierarchy/
>>
>> Measuring Cache Efficiency
>>
>> GPU profilers like NVIDIA Nsight, AMD Radeon GPU Profiler, and RenderDoc
>> expose cache hit rates and memory throughput. Key metrics to watch:
> 
> nothing. That's too located close to the same cpu, idiot. It has nothing
> to do with anything. This cretin dontt undrestand what a cache is. He
> thinks it's ram.
> 

[toc] | [prev] | [next] | [standalone]

#671507 — Where is micro penis mental error? (Re: Well thats good, co-location, onto the same processor die)

Hi,

Maybe micro penis thinks if   assign 50% of my
32 GB memory, i.e. 16 GB to the GPU. That
the CPU can not anymore access it?

Traditional Integrated GPUs: When you manually
carve out 16 GB for the GPU in the BIOS, you
are creating a hard software partition. The
system locks that 16 GB exclusively for the
GPU to ensure it always has video memory.
While the CPU is physically wired to those
RAM chips, the operating system's memory
manager blocks the CPU from using that 16 GB
for general applications to prevent crashes.

Modern Unified Memory:
If you are using a chip like an Apple M-series,
there is no fixed partition. The CPU and GPU share
a single pool of 32 GB. If the GPU needs 16 GB for
an AI model, it allocates it dynamically. The CPU
can still read and write to that exact same 16 GB
address space simultaneously using shared pointers,
completely eliminating the need to copy data back and forth.

Bye

Mild Shock schrieb:
> Hi,
> 
>  > That's too located close to the same cpu, idiot.
> 
> Yes, colocating a CPU and GPU onto the same
> processor die or package provides massive b
> enefits, primarily by eliminating the latency
> and bandwidth bottlenecks of moving data
> across a motherboard.
> 
> Individual L1 Caches: Yes, the CPU cores and
> the GPU compute units (Streaming Multiprocessors /
> Compute Units) still maintain private,
> individual L1 caches.
> 
> The "Colocation" Benefit: In traditional
> setups (a separate CPU and GPU on PCIe slots),
> data must be copied from system RAM to the
> GPU's VRAM. When a CPU and GPU are colocated
> (like in Apple Silicon, AMD APUs, or Intel
> processors), they share a Unified Memory
> Architecture (UMA). Both processors can read
> and write to the exact same physical memory
> pool without redundant data copying
> 
> Shared Last-Level Cache: While the L1 caches
> remain separate, colocated architectures
> often share a high-capacity Last-Level
> Cache (L2 or L3). This allows the CPU and
> GPU to quickly pass data back and forth
> locally on the chip.
> 
> Bye
> 
> Zackee Mulatov schrieb:
>> Mild Shock wrote:
>>
>>> Just read something for once you alcoholic:
>>>
>>> GPU Cache Hierarchy: Understanding L1, L2, and VRAM
>>> https://charlesgrassi.dev/blog/gpu-cache-hierarchy/
>>>
>>> Measuring Cache Efficiency
>>>
>>> GPU profilers like NVIDIA Nsight, AMD Radeon GPU Profiler, and RenderDoc
>>> expose cache hit rates and memory throughput. Key metrics to watch:
>>
>> nothing. That's too located close to the same cpu, idiot. It has nothing
>> to do with anything. This cretin dontt undrestand what a cache is. He
>> thinks it's ram.
>>
> 

[toc] | [prev] | [next] | [standalone]

#671514 — Re: Well thats good, co-location, onto the same processor die (Was: GPU Cache Hierarchy: Understanding L1, L2, and VRAM)

Mild Shock wrote:

> Shared Last-Level Cache: While the L1 caches remain separate, colocated
> architectures often share a high-capacity Last-Level Cache (L2 or L3).
> This allows the CPU and GPU to quickly pass data back and forth locally
> on the chip.

this guy is a total failure in computing; the point is the gpu to do it's 
job without cpu intervention. That's why the name, gpu. The cpu is for 
other things

[toc] | [prev] | [next] | [standalone]

#671508 — Re: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov (Was: I'm a spinner, I'm a sinner [Dmitry Vyukov for pi-WAM])

On 7/19/2026 11:31 PM, Mild Shock wrote:
> Hi,
> 
> Its actually quite amazing. Gemini, DeepSeek,
> OpenAI all know Dmitriy V'jukov. I have asked
> the IntelliJ integrated Freeium AI to generate
> 
> some code for me, I guess their service uses
> by default OpenAI (Codex), and had it reviewed
> by Gemini and DeepSeek. These AIs started lecturing
> 
> me about lazySet() in Java. But I went with set():
> 
>      private static boolean enqueue(Queue q, Object data) {
>          int pos = q.enqueuePos.get();
>          for (; ; ) {
>              int index = pos & q.bufferMask;
>              int seq = q.sequences.get(index);
>              int dif = seq - pos;
>              if (dif == 0) {
>                  if (q.enqueuePos.compareAndSet(pos, pos + 1)) {
>                      q.data[index] = data;
>                      q.sequences.set(index, pos + 1);
>                      return true;
>                  }
>                  pos = q.enqueuePos.get();
>              } else if (dif < 0) {
>                  return false;
>              } else {
>                  pos = q.enqueuePos.get();
>              }
>          }
>      }
> 
> The above version seems to be more suitable
> for my purpose, since it allows polling, it
> basically implements offer(). While the
> 
> version posted on in the lock free group
> by Chris M. Thomasson implements a spin wait
> blocking put() already.

That had to be my bakery algo version for the bounded buffer. Now, it 
can avoid the spin wait with a futex, BUT, we have to be careful. 
Working with lock/wait-free algos, we need to know what we are doing. I 
happen to have a lot of experience with them.

If you read my conversation with my friend, we can mix and match the CAS 
version and my XADD version on demand.

[...]

[toc] | [prev] | [next] | [standalone]

#671509 — I didn't find Futex in WebGPU / WGSL (Was: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov)

Hi,

I didn't find Futex in WebGPU / WGSL.
The website WebGPU fundamentals is on
GitHub. I did a search here:

https://github.com/webgpu/webgpufundamentals

In Java I can use Doug Leas queue.
In WebGPU / WGSL I will mostlikely
adopt Dmitry Vyukov , for a first stab.

Who is Doug lea?

He wrote Concurrent Programming in
Java: Design Principles and Patterns
https://en.wikipedia.org/wiki/Doug_Lea

He is behind most of the concurrency promitives
in Java. Including the array backed queue that
I tested. Remember the results I had:

public class DmitryVyukov
8 ms
public class DougLea
10 ms

Bye

Chris M. Thomasson schrieb:
> On 7/19/2026 11:31 PM, Mild Shock wrote:
>> Hi,
>>
>> Its actually quite amazing. Gemini, DeepSeek,
>> OpenAI all know Dmitriy V'jukov. I have asked
>> the IntelliJ integrated Freeium AI to generate
>>
>> some code for me, I guess their service uses
>> by default OpenAI (Codex), and had it reviewed
>> by Gemini and DeepSeek. These AIs started lecturing
>>
>> me about lazySet() in Java. But I went with set():
>>
>>      private static boolean enqueue(Queue q, Object data) {
>>          int pos = q.enqueuePos.get();
>>          for (; ; ) {
>>              int index = pos & q.bufferMask;
>>              int seq = q.sequences.get(index);
>>              int dif = seq - pos;
>>              if (dif == 0) {
>>                  if (q.enqueuePos.compareAndSet(pos, pos + 1)) {
>>                      q.data[index] = data;
>>                      q.sequences.set(index, pos + 1);
>>                      return true;
>>                  }
>>                  pos = q.enqueuePos.get();
>>              } else if (dif < 0) {
>>                  return false;
>>              } else {
>>                  pos = q.enqueuePos.get();
>>              }
>>          }
>>      }
>>
>> The above version seems to be more suitable
>> for my purpose, since it allows polling, it
>> basically implements offer(). While the
>>
>> version posted on in the lock free group
>> by Chris M. Thomasson implements a spin wait
>> blocking put() already.
> 
> That had to be my bakery algo version for the bounded buffer. Now, it 
> can avoid the spin wait with a futex, BUT, we have to be careful. 
> Working with lock/wait-free algos, we need to know what we are doing. I 
> happen to have a lot of experience with them.
> 
> If you read my conversation with my friend, we can mix and match the CAS 
> version and my XADD version on demand.
> 
> [...]

[toc] | [prev] | [next] | [standalone]

#671510 — Re: I didn't find Futex in WebGPU / WGSL (Was: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov)

On 7/20/2026 2:25 PM, Mild Shock wrote:
> Hi,
> 
> I didn't find Futex in WebGPU / WGSL.
> The website WebGPU fundamentals is on
> GitHub. I did a search here:
> 
> https://github.com/webgpu/webgpufundamentals
> 
> In Java I can use Doug Leas queue.
> In WebGPU / WGSL I will mostlikely
> adopt Dmitry Vyukov , for a first stab.
> 
> Who is Doug lea?
> 
> He wrote Concurrent Programming in
> Java: Design Principles and Patterns
> https://en.wikipedia.org/wiki/Doug_Lea

A futex:

https://www.man7.org/linux/man-pages/man2/futex.2.html

For a compute shader? Afaict, no need for it at all. Actually, strive to 
avoid any atomic RMW! It can be done, but if you really need it:

imageAtomicAdd is a damn good one for accumulation buffers.

An example from some of my compute shader code:

void add_hit(ct_plane2d plane, vec2 p, vec3 weight)
{
     vec2 uv = ct_plane2d_unproject(plane, p);
     ivec2 px = ivec2(uv * u_resolution);

     if (px.x >= 0 && px.x < int(u_resolution.x) &&
         px.y >= 0 && px.y < int(u_resolution.y))
     {
         imageAtomicAdd(accum_r,    px, weight.r);
         imageAtomicAdd(accum_g,    px, weight.g);
         imageAtomicAdd(accum_b,    px, weight.b);
         imageAtomicAdd(accum_hits, px, 1.0f);
     }
}

[...]

[toc] | [prev] | [next] | [standalone]

#671511 — Re: I didn't find Futex in WebGPU / WGSL (Was: Gemini, DeepSeek, OpenAI all know Dmitriy V'jukov)

On 7/20/2026 2:32 PM, Chris M. Thomasson wrote:
> On 7/20/2026 2:25 PM, Mild Shock wrote:
>> Hi,
>>
>> I didn't find Futex in WebGPU / WGSL.
>> The website WebGPU fundamentals is on
>> GitHub. I did a search here:
>>
>> https://github.com/webgpu/webgpufundamentals
>>
>> In Java I can use Doug Leas queue.
>> In WebGPU / WGSL I will mostlikely
>> adopt Dmitry Vyukov , for a first stab.
>>
>> Who is Doug lea?
>>
>> He wrote Concurrent Programming in
>> Java: Design Principles and Patterns
>> https://en.wikipedia.org/wiki/Doug_Lea
> 
> A futex:
> 
> https://www.man7.org/linux/man-pages/man2/futex.2.html
> 
> For a compute shader? Afaict, no need for it at all. Actually, strive to 
> avoid any atomic RMW! It can be done, but if you really need it:
> 
> imageAtomicAdd is a damn good one for accumulation buffers.
> 
> An example from some of my compute shader code:
> 
> void add_hit(ct_plane2d plane, vec2 p, vec3 weight)
> {
>      vec2 uv = ct_plane2d_unproject(plane, p);
>      ivec2 px = ivec2(uv * u_resolution);
> 
>      if (px.x >= 0 && px.x < int(u_resolution.x) &&
>          px.y >= 0 && px.y < int(u_resolution.y))
>      {
>          imageAtomicAdd(accum_r,    px, weight.r);
>          imageAtomicAdd(accum_g,    px, weight.g);
>          imageAtomicAdd(accum_b,    px, weight.b);
>          imageAtomicAdd(accum_hits, px, 1.0f);
>      }
> }
> 
> [...]

You don't really want to "wait" for anything in a compute shader. If you 
must use CAS use it as a state machine. Not a damn loop. If you can 
manage it.

[toc] | [prev] | [next] | [standalone]

#671512 — There is no imageAtomicAdd in WGSL (Was: I didn't find Futex in WebGPU / WGSL)

Hi,

Hi,

I am developing agains WebGPU / WGSL.
And overview of WebGPU / WGSL is found here:

https://github.com/webgpu/webgpufundamentals

There is no imageAtomicAdd in WGSL.
imageAtomicAdd is from WebGL / GLSL.

These are two different things:

WebGPU / WGSL : Wrapper for Vulcan, Direct 12, or Metal
WebGL / GLSL : Wrapper for OpenGL

Chris M. Thomasson schrieb:
> On 7/20/2026 2:32 PM, Chris M. Thomasson wrote:
>> On 7/20/2026 2:25 PM, Mild Shock wrote:
>>> Hi,
>>>
>>> I didn't find Futex in WebGPU / WGSL.
>>> The website WebGPU fundamentals is on
>>> GitHub. I did a search here:
>>>
>>> https://github.com/webgpu/webgpufundamentals
>>>
>>> In Java I can use Doug Leas queue.
>>> In WebGPU / WGSL I will mostlikely
>>> adopt Dmitry Vyukov , for a first stab.
>>>
>>> Who is Doug lea?
>>>
>>> He wrote Concurrent Programming in
>>> Java: Design Principles and Patterns
>>> https://en.wikipedia.org/wiki/Doug_Lea
>>
>> A futex:
>>
>> https://www.man7.org/linux/man-pages/man2/futex.2.html
>>
>> For a compute shader? Afaict, no need for it at all. Actually, strive 
>> to avoid any atomic RMW! It can be done, but if you really need it:
>>
>> imageAtomicAdd is a damn good one for accumulation buffers.
>>
>> An example from some of my compute shader code:
>>
>> void add_hit(ct_plane2d plane, vec2 p, vec3 weight)
>> {
>>      vec2 uv = ct_plane2d_unproject(plane, p);
>>      ivec2 px = ivec2(uv * u_resolution);
>>
>>      if (px.x >= 0 && px.x < int(u_resolution.x) &&
>>          px.y >= 0 && px.y < int(u_resolution.y))
>>      {
>>          imageAtomicAdd(accum_r,    px, weight.r);
>>          imageAtomicAdd(accum_g,    px, weight.g);
>>          imageAtomicAdd(accum_b,    px, weight.b);
>>          imageAtomicAdd(accum_hits, px, 1.0f);
>>      }
>> }
>>
>> [...]
> 
> You don't really want to "wait" for anything in a compute shader. If you 
> must use CAS use it as a state machine. Not a damn loop. If you can 
> manage it.

[toc] | [prev] | [next] | [standalone]

#671513 — OpenGL is dead. Apple said bye bye / Wayland Compositor (Was: There is no imageAtomicAdd in WGSL)

Hi,

Apple officially deprecated OpenGL and
OpenGL ES back in macOS 10.14 (Mojave) in
2018 and iOS 12, sunsetting native
support in favor of Metal.

And then in the Windows and Linux world,
for surface management, there is Wayland
Compositor. But new GPUs that share system
memory, also help here.

Open-Source Drivers (amdgpu & mesa):
Unlike NVIDIA's historical proprietary
hurdles, AMD's graphics drivers are fully
open-source and built directly into
the Linux kernel and Mesa.

Native GBM Support: AMD's driver stack
natively and cleanly implements GBM
(Generic Buffer Management) and DRM/KMS,
which is the exact standard modern
Wayland compositors (like GNOME/Mutter,
KDE/KWin, Sway, and Hyprland) rely on
to allocate buffers and manage displays.

Unified Memory (APU Advantage): Because
an AMD APU shares system RAM between
the CPU and the integrated GPU, zero-copy
buffer sharing under Wayland is
exceptionally efficient.

Bye

Mild Shock schrieb:
> Hi,
> 
> Hi,
> 
> I am developing agains WebGPU / WGSL.
> And overview of WebGPU / WGSL is found here:
> 
> https://github.com/webgpu/webgpufundamentals
> 
> There is no imageAtomicAdd in WGSL.
> imageAtomicAdd is from WebGL / GLSL.
> 
> These are two different things:
> 
> WebGPU / WGSL : Wrapper for Vulcan, Direct 12, or Metal
> WebGL / GLSL : Wrapper for OpenGL
> 
> Chris M. Thomasson schrieb:
>> On 7/20/2026 2:32 PM, Chris M. Thomasson wrote:
>>> On 7/20/2026 2:25 PM, Mild Shock wrote:
>>>> Hi,
>>>>
>>>> I didn't find Futex in WebGPU / WGSL.
>>>> The website WebGPU fundamentals is on
>>>> GitHub. I did a search here:
>>>>
>>>> https://github.com/webgpu/webgpufundamentals
>>>>
>>>> In Java I can use Doug Leas queue.
>>>> In WebGPU / WGSL I will mostlikely
>>>> adopt Dmitry Vyukov , for a first stab.
>>>>
>>>> Who is Doug lea?
>>>>
>>>> He wrote Concurrent Programming in
>>>> Java: Design Principles and Patterns
>>>> https://en.wikipedia.org/wiki/Doug_Lea
>>>
>>> A futex:
>>>
>>> https://www.man7.org/linux/man-pages/man2/futex.2.html
>>>
>>> For a compute shader? Afaict, no need for it at all. Actually, strive 
>>> to avoid any atomic RMW! It can be done, but if you really need it:
>>>
>>> imageAtomicAdd is a damn good one for accumulation buffers.
>>>
>>> An example from some of my compute shader code:
>>>
>>> void add_hit(ct_plane2d plane, vec2 p, vec3 weight)
>>> {
>>>      vec2 uv = ct_plane2d_unproject(plane, p);
>>>      ivec2 px = ivec2(uv * u_resolution);
>>>
>>>      if (px.x >= 0 && px.x < int(u_resolution.x) &&
>>>          px.y >= 0 && px.y < int(u_resolution.y))
>>>      {
>>>          imageAtomicAdd(accum_r,    px, weight.r);
>>>          imageAtomicAdd(accum_g,    px, weight.g);
>>>          imageAtomicAdd(accum_b,    px, weight.b);
>>>          imageAtomicAdd(accum_hits, px, 1.0f);
>>>      }
>>> }
>>>
>>> [...]
>>
>> You don't really want to "wait" for anything in a compute shader. If 
>> you must use CAS use it as a state machine. Not a damn loop. If you 
>> can manage it.
> 

[toc] | [prev] | [next] | [standalone]

#671518 — Re: There is no imageAtomicAdd in WGSL (Was: I didn't find Futex in WebGPU / WGSL)

On 7/20/2026 3:12 PM, Mild Shock wrote:
> Hi,
> 
> Hi,
> 
> I am developing agains WebGPU / WGSL.
> And overview of WebGPU / WGSL is found here:
> 
> https://github.com/webgpu/webgpufundamentals
> 
> There is no imageAtomicAdd in WGSL.
> imageAtomicAdd is from WebGL / GLSL.
> 
> These are two different things:
> 
> WebGPU / WGSL : Wrapper for Vulcan, Direct 12, or Metal
> WebGL / GLSL : Wrapper for OpenGL
> 
> Chris M. Thomasson schrieb:
>> On 7/20/2026 2:32 PM, Chris M. Thomasson wrote:
>>> On 7/20/2026 2:25 PM, Mild Shock wrote:
>>>> Hi,
>>>>
>>>> I didn't find Futex in WebGPU / WGSL.
>>>> The website WebGPU fundamentals is on
>>>> GitHub. I did a search here:
>>>>
>>>> https://github.com/webgpu/webgpufundamentals
>>>>
>>>> In Java I can use Doug Leas queue.
>>>> In WebGPU / WGSL I will mostlikely
>>>> adopt Dmitry Vyukov , for a first stab.
>>>>
>>>> Who is Doug lea?
>>>>
>>>> He wrote Concurrent Programming in
>>>> Java: Design Principles and Patterns
>>>> https://en.wikipedia.org/wiki/Doug_Lea
>>>
>>> A futex:
>>>
>>> https://www.man7.org/linux/man-pages/man2/futex.2.html
>>>
>>> For a compute shader? Afaict, no need for it at all. Actually, strive 
>>> to avoid any atomic RMW! It can be done, but if you really need it:
>>>
>>> imageAtomicAdd is a damn good one for accumulation buffers.
>>>
>>> An example from some of my compute shader code:
>>>
>>> void add_hit(ct_plane2d plane, vec2 p, vec3 weight)
>>> {
>>>      vec2 uv = ct_plane2d_unproject(plane, p);
>>>      ivec2 px = ivec2(uv * u_resolution);
>>>
>>>      if (px.x >= 0 && px.x < int(u_resolution.x) &&
>>>          px.y >= 0 && px.y < int(u_resolution.y))
>>>      {
>>>          imageAtomicAdd(accum_r,    px, weight.r);
>>>          imageAtomicAdd(accum_g,    px, weight.g);
>>>          imageAtomicAdd(accum_b,    px, weight.b);
>>>          imageAtomicAdd(accum_hits, px, 1.0f);
>>>      }
>>> }
>>>
>>> [...]
>>
>> You don't really want to "wait" for anything in a compute shader. If 
>> you must use CAS use it as a state machine. Not a damn loop. If you 
>> can manage it.
> 

WebGL has compute shaders, right? So, imageAtomicAdd works.

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | sci.physics.relativity

csiph-web