From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH liburing] handle buffered writes in read-write test
Date: Mon, 15 Aug 2022 11:12:35 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 15 Aug 2022 10:09:14 -0700, Dylan Yudaken wrote:
> When buffered writes are used then two things change:
> 1 - signals will propogate to the submit() call (as they would be
> effectively ignored when going async)
> 2 - CQE ordering will change
>
> Fix the read-write for both of these cases by ignoring the signal and
> handling CQE ordering.
>
> [...]
Applied, thanks!
[1/1] handle buffered writes in read-write test
commit: 9adc7ddb158e773c48e25aa1fab7f9f6912a458e
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-08-15 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 17:09 [PATCH liburing] handle buffered writes in read-write test Dylan Yudaken
2022-08-15 17:12 ` Jens Axboe [this message]
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=166058355583.2374707.11623491940402389484.b4-ty@kernel.dk \
[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