Re: [go-nuts] Clarification of memory model behavior within a single goroutine

2023-01-22 Thread 'David Klempner' via golang-nuts
On Mon, Jan 23, 2023 at 11:38 AM Robert Engels wrote: > The atomic functions force a memory barrier when atomically in conjunction > with the atomic read of the same value. > > You could use CGO to call a C function to do what you desire - but it > shouldn’t be necessary. > C doesn't solve this

Re: [go-nuts] Realizing SSD random read IOPS

2017-05-17 Thread 'David Klempner' via golang-nuts
On May 16, 2017 22:03, "Ian Lance Taylor" wrote: On Tue, May 16, 2017 at 9:26 PM, Manish Rai Jain wrote: >> The runtime will spawn a new thread to replace the one that is blocked. > > Realized that after writing my last mail. And that actually explains some of > the other crashes we saw, about "