Now that io_uring will be in the upcoming 5.1 kernel, I spent some time writing up how it came to be and how it works. More formats likely coming, and I expect a few revisions too. For now, consider this v1.0 of the doc: http://kernel.dk/io_uring.pdf
-
Prikaži ovu nit
-
Odgovor korisniku/ci @axboe
I am confused on your definition of read_barrier() and write_barrier(). Are you reusing something defined elsewhere such as... * https://www.kernel.org/doc/Documentation/memory-barriers.txt … * https://www.modernescpp.com/index.php/fences-as-memory-barriers …
1 reply 0 proslijeđenih tweetova 1 korisnik označava da mu se sviđa
Odgovor korisniku/ci @MarkCallaghanDB
I'd rather just defer to liburing, which got changed to using acquire/release semantics for this.
10:57 - 4. pro 2019.
0 replies
0 proslijeđenih tweetova
1 korisnik označava da mu se sviđa
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.