Twitter | Pretraživanje | |
Jens Axboe
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:
Reply Retweet Označi sa "sviđa mi se" More
Jens Axboe 6. tra
Odgovor korisniku/ci @axboe
Do let me know if you have any comments. Anything from "you spelled this word wrong" to "I wish it included X" would be appreciated.
Reply Retweet Označi sa "sviđa mi se"
Jens Axboe 8. tra
Odgovor korisniku/ci @axboe
Fixed the various typos and missing '*' that were reported, and added a small blurb on io_uring_get_completion() as well, and pushed it out. Same link. Bottom line will show versioning, this one should read 0.2.
Reply Retweet Označi sa "sviđa mi se"
Mark Callaghan 4. pro
Odgovor korisniku/ci @axboe
Have you published any results with fio that compare io_uring with mmap for uncached data?
Reply Retweet Označi sa "sviđa mi se"
Jens Axboe 4. pro
Odgovor korisniku/ci @MarkCallaghanDB
I have not, but that would be trivial to do. Let me know what kind of test exactly you'd want to see and I can run it.
Reply Retweet Označi sa "sviđa mi se"
Mark Callaghan 4. pro
Odgovor korisniku/ci @axboe
Reading now. Happy to see ioprio but not sure what priority levels 0 to 7 for IOPRIO_CLASS_{RT,BE} interact. How can I learn more about that? Looking at this now -
Reply Retweet Označi sa "sviđa mi se"
Jens Axboe 4. pro
Odgovor korisniku/ci @MarkCallaghanDB
I don't think that part is very interesting, since CFQ is gone and only BFQ supports priorities. They do map all the way down to the driver though, so hardware support is trivial.
Reply Retweet Označi sa "sviđa mi se"
Zach Bjornson 6. tra
Odgovor korisniku/ci @axboe
Very helpful article (and API)! Last night I started playing with liburing for Node.js. Got it working in wait mode, still trying to get polling to work. Hitting a segfault in your polling test app that I haven't narrowed down yet.
Reply Retweet Označi sa "sviđa mi se"
Jens Axboe 6. tra
Odgovor korisniku/ci @Zbjorn
Which test case is segfaulting? If you help me reproduce, I'm sure it's an easy fix.
Reply Retweet Označi sa "sviđa mi se"
Mark Callaghan 4. pro
Odgovor korisniku/ci @axboe
I am confused on your definition of read_barrier() and write_barrier(). Are you reusing something defined elsewhere such as... * *
Reply Retweet Označi sa "sviđa mi se"
Jens Axboe 4. pro
Odgovor korisniku/ci @MarkCallaghanDB
I'd rather just defer to liburing, which got changed to using acquire/release semantics for this.
Reply Retweet Označi sa "sviđa mi se"