public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Andreas Wagner <andreasw3756@gmail.com>, io-uring@vger.kernel.org
Subject: Re: A write to a TCP-stream overtook another write
Date: Wed, 30 Apr 2025 19:47:56 +0100	[thread overview]
Message-ID: <3738954c-d6fb-4071-be4c-0673f69863e3@gmail.com> (raw)
In-Reply-To: <edf639304e2401047a791b2de7254f7613a390a1.camel@gmail.com>

On 4/30/25 16:33, Andreas Wagner wrote:
> Dear everyone,
> 
> during development of an HTTP-server, I ran into a problem: A write to
> a TCP-stream overtook another write to the same stream.

Requests can be reordered in many ways, you can't submit two requests
to a tcp socket and expect that they'll get executed in order. It was
mentioned many times before, for example, look through this thread:

https://github.com/axboe/liburing/issues/1359

-- 
Pavel Begunkov


      reply	other threads:[~2025-04-30 18:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 15:33 A write to a TCP-stream overtook another write Andreas Wagner
2025-04-30 18:47 ` Pavel Begunkov [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 \
    --in-reply-to=3738954c-d6fb-4071-be4c-0673f69863e3@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=andreasw3756@gmail.com \
    --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