From: Pavel Begunkov <asml.silence@gmail.com>
To: Brian Gianforcaro <b.gianfo@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] io_uring: batch getting pcpu references
Date: Mon, 30 Dec 2019 21:45:28 +0300 [thread overview]
Message-ID: <b1ba1740-d058-fffe-faa8-0f431ecfa0d3@gmail.com> (raw)
In-Reply-To: <20191230033321.kg2e4ijj2w3ut36l@lmao.redmond.corp.microsoft.com>
[-- Attachment #1.1: Type: text/plain, Size: 784 bytes --]
On 30/12/2019 06:33, Brian Gianforcaro wrote:
>>>>> +static void __io_req_free_empty(struct io_kiocb *req)
>>>>
>>>> If anybody have better naming (or a better approach at all), I'm all ears.
>>>
>>> __io_req_do_free()?
>>
>> Not quite clear what's the difference with __io_req_free() then
>>
>>>
>>> I think that's better than the empty, not quite sure what that means.
>>
>> Probably, so. It was kind of "request without a bound sqe".
>> Does io_free_{hollow,empty}_req() sound better?
>
> Given your description, perhaps io_free_unbound_req() makes sense?
>
Like it more, though neither of these have a set meaning in io_uring context.
The patch already got into Jen's repo, so you can send another one, if you
think it's worth it.
--
Pavel Begunkov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-12-30 18:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 22:28 [PATCH 0/2] optimise ctx's refs grabbing in io_uring Pavel Begunkov
2019-12-17 22:28 ` [PATCH 1/2] pcpu_ref: add percpu_ref_tryget_many() Pavel Begunkov
2019-12-17 23:42 ` Jens Axboe
2019-12-18 16:26 ` Tejun Heo
2019-12-18 17:49 ` Dennis Zhou
2019-12-21 15:36 ` Pavel Begunkov
2019-12-17 22:28 ` [PATCH 2/2] io_uring: batch getting pcpu references Pavel Begunkov
2019-12-17 23:21 ` Jens Axboe
2019-12-17 23:31 ` Jens Axboe
2019-12-18 9:25 ` Pavel Begunkov
2019-12-18 9:23 ` Pavel Begunkov
2019-12-18 0:02 ` Jens Axboe
2019-12-18 10:41 ` Pavel Begunkov
2019-12-21 16:15 ` [PATCH v2 0/3] optimise ctx's refs grabbing in io_uring Pavel Begunkov
2019-12-21 16:15 ` [PATCH v2 1/3] pcpu_ref: add percpu_ref_tryget_many() Pavel Begunkov
2019-12-21 16:15 ` [PATCH v2 2/3] io_uring: batch getting pcpu references Pavel Begunkov
2019-12-21 16:15 ` [PATCH RFC v2 3/3] io_uring: batch get(ctx->ref) across submits Pavel Begunkov
2019-12-21 16:20 ` Pavel Begunkov
2019-12-21 16:38 ` Jens Axboe
2019-12-21 16:48 ` Pavel Begunkov
2019-12-21 17:01 ` Jens Axboe
2019-12-21 17:26 ` Pavel Begunkov
2019-12-21 20:12 ` [PATCH v3 0/2] optimise ctx's refs grabbing in io_uring Pavel Begunkov
2019-12-21 20:12 ` [PATCH v3 1/2] pcpu_ref: add percpu_ref_tryget_many() Pavel Begunkov
2019-12-21 20:12 ` [PATCH v3 2/2] io_uring: batch getting pcpu references Pavel Begunkov
2019-12-21 21:56 ` Pavel Begunkov
2019-12-28 11:13 ` [PATCH v4 0/2] optimise ctx's refs grabbing in io_uring Pavel Begunkov
2019-12-28 11:13 ` [PATCH v4 1/2] pcpu_ref: add percpu_ref_tryget_many() Pavel Begunkov
2019-12-28 11:13 ` [PATCH v4 2/2] io_uring: batch getting pcpu references Pavel Begunkov
2019-12-28 11:15 ` Pavel Begunkov
2019-12-28 17:03 ` Jens Axboe
2019-12-28 18:37 ` Pavel Begunkov
2019-12-30 3:33 ` Brian Gianforcaro
2019-12-30 18:45 ` Pavel Begunkov [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=b1ba1740-d058-fffe-faa8-0f431ecfa0d3@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=b.gianfo@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).