From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH] io_uring: hide uring_fd in ctx
Date: Thu, 16 Jan 2020 21:47:29 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <2aefced4902f33f2b70aaedc32bc8d60a20efd7a.1579225489.git.asml.silence@gmail.com>
On 1/16/20 6:45 PM, Pavel Begunkov wrote:
> req->ring_fd and req->ring_file are used only during the prep stage
> during submission, which is is protected by mutex. There is no need
> to store them per-request, place them in ctx.
Thanks, applied.
--
Jens Axboe
prev parent reply other threads:[~2020-01-17 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 1:45 [PATCH] io_uring: hide uring_fd in ctx Pavel Begunkov
2020-01-17 4:47 ` 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 \
[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