From: Mark Reed <[email protected]>
To: "io-uring" <[email protected]>
Subject: io_uring_prep_writev
Date: Sun, 24 Nov 2019 07:34:09 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To:
Jens et al,
I wrote a C event loop library based on io_uring and a KV store similar to memcached using it. Mrcache is 4x faster using io_uring vs epoll so thank you guys for the work on this. I'm looking forward to 5.5 and am testing on 5.2.14 right now.
https://github.com/MarkReedZ/mrloop
https://github.com/MarkReedZ/mrcache
I'm currently using write instead of io_uring_prep_writev when writing to the socket and have a couple questions:
1. If I queue up 50 writevs to a socket will they write in order?
2. If the client backs up will those writevs return or will they simply wait?
3. Would you expect io_uring_prep_writev to be faster than using write on the socket? My initial benchmarks had a 50 deep GET pipeline which would do a single writev with 50 iovs and that was slower than copying to an output buffer and looping on write when full. Perhaps I had something wrong with the benchmark at the time - if you think so I'll try again.
Thanks again,
Mark
next reply other threads:[~2019-11-24 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-24 15:34 Mark Reed [this message]
2019-11-24 16:42 ` io_uring_prep_writev Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16e9e0c80e0.10e8cb6351147499.7149684061226631446@untilfluent.com \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox