From: Jens Axboe <[email protected]>
To: Al Viro <[email protected]>
Cc: Linus Torvalds <[email protected]>,
io-uring <[email protected]>
Subject: Re: [GIT PULL] iov_iter retry fixes
Date: Fri, 17 Sep 2021 08:51:35 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/17/21 8:49 AM, Al Viro wrote:
> On Fri, Sep 17, 2021 at 08:44:32AM -0600, Jens Axboe wrote:
>> Hi Linus,
>>
>> This adds a helper to save/restore iov_iter state, and modifies io_uring
>> to use it. After that is done, we can kill the iter->truncated addition
>> that we added for this release. The io_uring change is being overly
>> cautious with the save/restore/advance, but better safe than sorry and
>> we can always improve that and reduce the overhead if it proves to be of
>> concern. The only case to be worried about in this regard is huge IO,
>> where iteration can take a while to iterate segments.
>>
>> I spent some time writing test cases, and expanded the coverage quite a
>> bit from the last posting of this. liburing carries this regression test
>> case now:
>>
>> https://git.kernel.dk/cgit/liburing/tree/test/file-verify.c
>>
>> which exercises all of this. It now also supports provided buffers, and
>> explicitly tests for end-of-file/device truncation as well.
>>
>> On top of that, Pavel sanitized the IOPOLL retry path to follow the
>> exact same pattern as normal IO.
>
> I can live with that; I do have problems with io-uring and its interactions
> with iov_iter, but those are mostly independent from the stuff you are
> doing here.
I actually think we can end up cleaning up some of those bits post this,
it'll definitely make it easier by having clean save/restore states.
--
Jens Axboe
next prev parent reply other threads:[~2021-09-17 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 14:44 [GIT PULL] iov_iter retry fixes Jens Axboe
2021-09-17 14:49 ` Al Viro
2021-09-17 14:51 ` Jens Axboe [this message]
2021-09-17 16:29 ` pr-tracker-bot
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] \
[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