From: Jens Axboe <[email protected]>
To: Dmitry Sychov <[email protected]>, [email protected]
Subject: Re: First kernel version with uring sockets support
Date: Wed, 22 Jan 2020 11:11:23 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CADPKF+cOiZ9ydRVzpj1GN4amjzoyH1Y_NRA7PZ4CLPpb-FrYfQ@mail.gmail.com>
On 1/22/20 11:08 AM, Dmitry Sychov wrote:
> It's unclear starting from what version the kernel and headers
> were updated with sockets support(IORING_OP_ACCEPT etc).
>
> I just checked today 2020/01/22 Focal Rossa Ubuntu and the last OP is
> only IORING_OP_TIMEOUT (still on kernel 5.4.0-12) ;(
Yeah, you'll need 5.5 for that.
> So maybe it's a good idea to comment-update every io_uring.h OP with
> minimum kernel version requirement...
You mean the one in liburing?
> p.s. Not every Linux user is a kernel hacker ;)
Definitely! This will be solved with 5.6 that introduces a probe
command, so you can query the running kernel for what opcodes it
supports. For now, it's not that easy, unfortunately...
--
Jens Axboe
next prev parent reply other threads:[~2020-01-22 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 18:08 First kernel version with uring sockets support Dmitry Sychov
2020-01-22 18:11 ` Jens Axboe [this message]
2020-01-22 18:22 ` Dmitry Sychov
2020-01-22 18:25 ` 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] \
/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