From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
Hao Xu <[email protected]>
Cc: [email protected], [email protected],
Jiufei Xue <[email protected]>,
Joseph Qi <[email protected]>
Subject: Re: [PATCH v3 RESEND] io_uring: add timeout support for io_uring_enter()
Date: Wed, 4 Nov 2020 12:34:00 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/4/20 12:27 PM, Pavel Begunkov wrote:
> On 04/11/2020 18:32, Jens Axboe wrote:
>> On 11/4/20 10:50 AM, Jens Axboe wrote:
>>> +struct io_uring_getevents_arg {
>>> + sigset_t *sigmask;
>>> + struct __kernel_timespec *ts;
>>> +};
>>> +
>>
>> I missed that this is still not right, I did bring it up in your last
>> posting though - you can't have pointers as a user API, since the size
>> of the pointer will vary depending on whether this is a 32-bit or 64-bit
>> arch (or 32-bit app running on 64-bit kernel).
>
> Maybe it would be better
>
> 1) to kill this extra indirection?
>
> struct io_uring_getevents_arg {
> - sigset_t *sigmask;
> - struct __kernel_timespec *ts;
> + sigset_t sigmask;
> + struct __kernel_timespec ts;
> };
>
> then,
>
> sigset_t *sig = (...)arg;
> __kernel_timespec* ts = (...)(arg + offset);
But then it's kind of hard to know which, if any, of them are set... I
did think about this, and any solution seemed worse than just having the
extra indirection.
Yeah, not doing the extra indirection would save a copy, but don't think
it's worth it for this path.
--
Jens Axboe
next prev parent reply other threads:[~2020-11-04 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 8:50 [PATCH v3] io_uring: add timeout support for io_uring_enter() Hao Xu
2020-11-03 2:54 ` [PATCH v3 RESEND] " Hao Xu
2020-11-04 17:50 ` Jens Axboe
2020-11-04 18:32 ` Jens Axboe
2020-11-04 19:06 ` Jens Axboe
2020-11-04 19:27 ` Pavel Begunkov
2020-11-04 19:34 ` Jens Axboe [this message]
2020-11-04 20:16 ` Pavel Begunkov
2020-11-04 20:28 ` Jens Axboe
2020-11-04 20:50 ` Jens Axboe
2020-11-04 21:20 ` Pavel Begunkov
2020-11-04 21:27 ` Jens Axboe
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] \
[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