From: Stefan Metzmacher <metze@samba.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: Re: Problems replacing epoll with io_uring in tevent
Date: Thu, 27 Oct 2022 20:35:58 +0200 [thread overview]
Message-ID: <c21825d5-a342-f204-a9a7-3c1c9a7d626c@samba.org> (raw)
In-Reply-To: <fedaf2e7-8a71-2fb2-5d7f-a03c01f824ba@kernel.dk>
Am 27.10.22 um 14:12 schrieb Jens Axboe:
> On 10/27/22 2:51 AM, Stefan Metzmacher wrote:
>> Hi Jens,
>>
>>> No problem - have you been able to test the current repo in general? I want to
>>> cut a 2.3 release shortly, but since that particular change impacts any kind of
>>> cqe waiting, would be nice to have a bit more confidence in it.
>>
>> Is 2.3 designed to be useful for 6.0 or also 6.1?
>
> 2.3 should be uptodate as of 6.0, don't want to release a new version
> that has bits from a kernel release that hasn't happened yet. The
> plan is to roughly do a liburing release at the same cadence as the
> kernel releases. Not that they are necessarily linked, but some features
> do obviously happen in lockstep like that.
>
>> Maybe wait for IORING_SEND_ZC_REPORT_USAGE to arrive?
>
> That'll be 2.4.
Ok, fine.
metze
next prev parent reply other threads:[~2022-10-27 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 14:42 Problems replacing epoll with io_uring in tevent Stefan Metzmacher
2022-10-26 16:00 ` Stefan Metzmacher
2022-10-26 17:08 ` Jens Axboe
2022-10-26 17:41 ` Pavel Begunkov
2022-10-27 8:18 ` Stefan Metzmacher
2022-10-27 8:05 ` Stefan Metzmacher
2022-10-27 19:25 ` Stefan Metzmacher
2022-12-28 16:19 ` Stefan Metzmacher
2023-01-18 15:56 ` Jens Axboe
2023-02-01 20:29 ` Stefan Metzmacher
2022-10-27 8:51 ` Stefan Metzmacher
2022-10-27 12:12 ` Jens Axboe
2022-10-27 18:35 ` Stefan Metzmacher [this message]
2022-10-27 19:54 ` Stefan Metzmacher
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=c21825d5-a342-f204-a9a7-3c1c9a7d626c@samba.org \
--to=metze@samba.org \
--cc=axboe@kernel.dk \
--cc=io-uring@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).