From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Cc: [email protected]
Subject: Re: [PATCH v2] io_uring: kbuf: add comments for some tricky code
Date: Fri, 17 Jun 2022 05:38:14 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 17 Jun 2022 13:04:29 +0800, Hao Xu wrote:
> From: Hao Xu <[email protected]>
>
> Add comments to explain why it is always under uring lock when
> incrementing head in __io_kbuf_recycle. And rectify one comemnt about
> kbuf consuming in iowq case.
>
>
> [...]
Applied, thanks!
[1/1] io_uring: kbuf: add comments for some tricky code
commit: 0efaf0d19e9e1271f2275393e62f709907cd40e2
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-17 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 5:04 [PATCH v2] io_uring: kbuf: add comments for some tricky code Hao Xu
2022-06-17 11:38 ` 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=165546589464.253852.4276960984454502097.b4-ty@kernel.dk \
[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