From: Artyom Pavlov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: Adding read_exact and write_all OPs?
Date: Tue, 16 Aug 2022 20:11:05 +0300 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Is there a tracking list of potential features for io-uring?
Unfortunately, I am not a C programmer (I mostly work with Rust), so I
probably would not be able to implement it myself.
But either way, could you point to relevant parts of code? In theory the
changes look relatively simple, but I am not sure how hard it will be to
implement the new OP codes in practice.
Best regards,
Artyom Pavlov.
next prev parent reply other threads:[~2022-08-16 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 21:04 Adding read_exact and write_all OPs? Artyom Pavlov
2022-08-03 15:01 ` Jens Axboe
2022-08-16 17:11 ` Artyom Pavlov [this message]
2022-08-16 18:46 ` Stefan Metzmacher
2022-08-17 10:36 ` Pavel Begunkov
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 \
[email protected] \
[email protected] \
[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