public inbox for [email protected]
 help / color / mirror / Atom feed
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:25:14 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CADPKF+d_B=CqL1cYttB-8H2n5XTHth_auUMM3B+2yPuc3g9q4w@mail.gmail.com>

On 1/22/20 11:22 AM, Dmitry Sychov wrote:
>> You mean the one in liburing?
> 
> I'am referring to
> https://github.com/frevib/io_uring-echo-server/blob/master/src/include/liburing/io_uring.h
> with sockets OPs as the latest interface reference, thinking it will
> help the io_uring newcomers if
> IORING_OP_* lines will have corresponding comments of the minimum
> kernel requirement for now and the future.

The above obviously isn't mine, but it's probably forked/pulled from my
liburing.

I think the best thing to do here is update the io_uring_enter(2)
man page, since it has opcode descriptions. In those descriptions,
each of them should include "Supported since version 5.x" to make
this perfectly clear.

Longer term, I expect the probe to be the most useful for applications.

I don't want to change io_uring.h itself, as I've keep that sane so it
can simply be copied from the kernel repository to liburing. I intend
to keep it that way.

-- 
Jens Axboe


      reply	other threads:[~2020-01-22 18:25 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
2020-01-22 18:22   ` Dmitry Sychov
2020-01-22 18:25     ` 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] \
    /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