public inbox for [email protected]
 help / color / mirror / Atom feed
From: Constantine Gavrilov <[email protected]>
To: [email protected], Jens Axboe <[email protected]>
Subject: Re: Re: io_uring_enter() with opcode IORING_OP_RECV ignores MSG_WAITALL in msg_flags
Date: Wed, 23 Mar 2022 15:12:00 +0200	[thread overview]
Message-ID: <CAAL3td2kwj4Gf-q1zpVUpSgNKFKwXq0biuu7TF6um8ZAQaQo2Q@mail.gmail.com> (raw)
In-Reply-To: <DM6PR15MB2603162E692B5A68A4FD0A6FFA189@DM6PR15MB2603.namprd15.prod.outlook.com>

> From: Jens Axboe <[email protected]>
> Sent: Wednesday, March 23, 2022 14:19
> To: Constantine Gavrilov <[email protected]>; [email protected] <[email protected]>
> Cc: io-uring <[email protected]>
> Subject: [EXTERNAL] Re: io_uring_enter() with opcode IORING_OP_RECV ignores MSG_WAITALL in msg_flags
>
> On 3/23/22 4:31 AM, Constantine Gavrilov wrote:
> > I get partial receives on TCP socket, even though I specify
> > MSG_WAITALL with IORING_OP_RECV opcode. Looking at tcpdump in
> > wireshark, I see entire reassambled packet (+4k), so it is not a
> > disconnect. The MTU is smaller than 4k.
> >
> > From the mailing list history, looks like this was discussed before
> > and it seems the fix was supposed to be in. Can someone clarify the
> > expected behavior?
> >
> > I do not think rsvmsg() has this issue.
>
> Do you have a test case? I added the io-uring list, that's the
> appropriate forum for this kind of discussion.
>
> --
> Jens Axboe

Yes, I have a real test case. I cannot share it vebratim, but with a
little effort I believe I can come with a simple code of
client/server.

It seems the issue shall be directly seen from the implementation, but
if it is not so, I will provide a sample code.

Forgot to mention that the issue is seen of Fedora kernel version
5.16.12-200.fc35.x86_64.

--
It seems the issue shall be directly seen from the implementation, but
if it is not so, I will provide a sample code.

Forgot to mention that the issue is seen of Fedora kernel version
5.16.12-200.fc35.x86_64.



-- 
----------------------------------------
Constantine Gavrilov
Storage Architect
Master Inventor
Tel-Aviv IBM Storage Lab
1 Azrieli Center, Tel-Aviv
----------------------------------------

  parent reply	other threads:[~2022-03-23 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BYAPR15MB260078EC747F0F0183D1BB1BFA189@BYAPR15MB2600.namprd15.prod.outlook.com>
2022-03-23 12:19 ` io_uring_enter() with opcode IORING_OP_RECV ignores MSG_WAITALL in msg_flags Jens Axboe
2022-03-23 12:32   ` Constantine Gavrilov
2022-03-23 12:38     ` Jens Axboe
     [not found]     ` <DM6PR15MB2603162E692B5A68A4FD0A6FFA189@DM6PR15MB2603.namprd15.prod.outlook.com>
2022-03-23 13:12       ` Constantine Gavrilov [this message]
2022-03-23 15:25         ` Jens Axboe
2022-03-23 19:40   ` Pavel Begunkov

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=CAAL3td2kwj4Gf-q1zpVUpSgNKFKwXq0biuu7TF6um8ZAQaQo2Q@mail.gmail.com \
    [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