Jens Axboe

@axboe

Linux kernel IO dabbler @ Facebook

Park City, Utah
Vrijeme pridruživanja: ožujak 2009.

Tweetovi

Blokirali ste korisnika/cu @axboe

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @axboe

  1. Prikvačeni tweet
    6. tra 2019.

    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:

    Prikaži ovu nit
    Poništi
  2. 31. sij
    Poništi
  3. 30. sij

    Busy updating io_uring man pages. Making everything current, but also including kernel version availability of previous features. You can always find the up-to-date set in liburing - at least for now, at some point I'll try and push these to the normal man pages package.

    Poništi
  4. 30. sij

    5.6 merge window changes for io_uring have now been merged. So many goodies in there, can't wait to see how 5.7 shapes up in the coming months.

    Poništi
  5. 29. sij
    Poništi
  6. proslijedio/la je Tweet
    28. sij

    [$] Some 5.5 kernel development statistics

    Poništi
  7. proslijedio/la je Tweet
    28. sij

    Initial implementation of io_uring for seastar posted. Need to do more testing, polish some details, and find some annoying bugs. But looking good!

    Poništi
  8. proslijedio/la je Tweet
    24. sij

    io_uring based transport layer for ASP․NET? Yes please! A very early prototype, rough edges, missing features but LOTs of fun! Feel free to leave a comment or even better, a commit :)

    Poništi
  9. 24. sij

    Always appreciate when Jon writes up some of my work, he does it so much better than I can.

    Poništi
  10. proslijedio/la je Tweet
    24. sij

    I'll be giving a short talk at FOSDEM this year in the room on modern systems engineering: * why io_uring will replace your IO stack * high concurrency DB techniques * bucking conv. wisdom on error handling If you're around come say hi :)

    Poništi
  11. proslijedio/la je Tweet
    24. sij

    just FYI, io_uring has been so far an extreme pleasure to work with. Most of the time I am spending is on refactoring and on the fact that seastar will have to keep supporting the old aio api. If we were starting from scratch with io_uring today it'd be even easier

    Poništi
  12. proslijedio/la je Tweet
    23. sij
    Poništi
  13. 24. sij

    Was great to meet you and discuss io_uring and netty (and just tech in general too). Already sparked a small patch set:

    Poništi
  14. proslijedio/la je Tweet
    21. sij
    Odgovor korisnicima

    The libunifex project by demonstrates using sender/receiver with io_uring.

    Poništi
  15. 21. sij

    I've changed the liburing license from LGPL to dual licensed LGPL/MIT. This should make it easier for some folks to adopt.

    Poništi
  16. proslijedio/la je Tweet
    19. sij

    vs : simple echo server. io_uring +99% performance, -45% cpu usage. Wow. . 🏆io_uring🏆. Try for yourself: io_uring: epoll:

    Poništi
  17. 15. sij

    It's a great honor, hope I can live up to it! Below is how I see myself recruiting new speakers.

    Poništi
  18. proslijedio/la je Tweet
    14. sij

    Heya heya! 9th edition of Kernel Recipes will take place in Paris, 28 to 30th september 2020. Stay tuned!

    Poništi
  19. proslijedio/la je Tweet
    13. sij

    Just cut rio 0.6.2 which automatically handles submission, removing another potential source of misuse for folks who want to take advantage of incredible io_uring perf in . io_uring is a goldrush for file and network IO. This changes everything.

    Poništi
  20. proslijedio/la je Tweet

    One of my very favorite graphs.

    Poništi
  21. proslijedio/la je Tweet
    6. sij

    Just cut rio 0.5! It's a pure-rust misuse-resistant io_uring library. io_uring will change everything about IO. The goldrush has started but folks don't realize it yet. lifetimes+RAII tricks ensure safety. go measure the o_direct example vs what you currently use :]

    Poništi

Č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.

    Možda bi vam se svidjelo i ovo:

    ·