public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Daniele Salvatore Albano <[email protected]>
Cc: [email protected]
Subject: Re: Keep getting the same buffer ID when RECV with IOSQE_BUFFER_SELECT
Date: Fri, 3 Jul 2020 13:12:55 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKq9yRjSewr5z2r8G7dt68RBX4VA9phGpFumKCipNgLzXMdcdQ@mail.gmail.com>

On 7/3/20 1:09 PM, Daniele Salvatore Albano wrote:
> On Fri, 3 Jul 2020, 20:57 Jens Axboe, <[email protected] <mailto:[email protected]>> wrote:
> 
>     On 7/3/20 12:48 PM, Daniele Salvatore Albano wrote:
>     > Hi,
>     >
>     > I have recently started to play with io_uring and liburing but I am
>     > facing an odd issue, of course initially I thought it was my code but
>     > after further investigation and testing some other code (
>     > https://github.com/frevib/io_uring-echo-server/tree/io-uring-op-provide-buffers
>     > ) I faced the same behaviour.
>     >
>     > When using the IOSQE_BUFFER_SELECT with RECV I always get the first
>     > read right but all the subsequent return a buffer id different from
>     > what was used by the kernel.
>     >
>     > The problem starts to happen only after io_uring_prep_provide_buffers
>     > is invoked to put back the buffer, the bid set is the one from cflags
>     >>> 16.
>     >
>     > The logic is as follow:
>     > - io_uring_prep_provide_buffers + io_uring_submit + io_uring_wait_cqe
>     > initialize all the buffers at the beginning
>     > - within io_uring_for_each_cqe, when accepting a new connection a recv
>     > sqe is submitted with the IOSQE_BUFFER_SELECT flag
>     > - within io_uring_for_each_cqe, when recv a send sqe is submitted
>     > using as buffer the one specified in cflags >> 16
>     > - within io_uring_for_each_cqe, when send a provide buffers for the
>     > bid used to send the data and a recv sqes are submitted.
>     >
>     > If I drop io_uring_prep_provide_buffers both in my code and in the
>     > code I referenced above it just works, but of course at some point
>     > there are no more buffers available.
>     >
>     > To further debug the issue I reduced the amount of provided buffers
>     > and started to print out the entire bufferset and I noticed that after
>     > the first correct RECV the kernel stores the data in the first buffer
>     > of the group id but always returns the last buffer id.
>     > It is like after calling io_uring_prep_provide_buffers the information
>     > on the kernel side gets corrupted, I tried to follow the logic on the
>     > kernel side but there is nothing apparent that would make me
>     > understand why I am facing this behaviour.
>     >
>     > The original author of that code told me on SO that he wrote & tested
>     > it on the kernel 5.6 + the provide buffers branch, I am facing this
>     > issue with 5.7.6, 5.8-rc1 and 5.8-rc3. The liburing library is built
>     > out of the branch, I didn't do too much testing with different
>     > versions but I tried to figure out where the issue was for the last
>     > week and within this period I have pulled multiple times the repo.
>     >
>     > Any hint or suggestion?
> 
>     Do you have a simple test case for this that can be run standalone?
>     I'll take a look, but I'd rather not spend time re-creating a test case
>     if you already have one.
> 
>     -- 
>     Jens Axboe
> 
> 
> I will shrink down the code to produce a simple test case but not sure
> how much code I will be able to lift because it's showing this
> behaviour on a second recv of a connection so I will need to keep all
> the boilerplate code to get there. 

That's fine, I'm just looking to avoid having to write it from scratch.
Plus a test case is easier to deal with than trying to write a test case
based on your description, less room for interpretative errors.

-- 
Jens Axboe


  parent reply	other threads:[~2020-07-03 19:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03 18:48 Keep getting the same buffer ID when RECV with IOSQE_BUFFER_SELECT Daniele Salvatore Albano
2020-07-03 18:57 ` Jens Axboe
     [not found]   ` <CAKq9yRjSewr5z2r8G7dt68RBX4VA9phGpFumKCipNgLzXMdcdQ@mail.gmail.com>
2020-07-03 19:12     ` Jens Axboe [this message]
2020-07-03 20:22       ` Daniele Salvatore Albano
2020-07-04 12:00         ` Hieke de Vries
2020-07-04 12:12           ` Daniele Salvatore Albano
2020-07-04 14:26             ` 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