netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Ronny Meeus' <ronny.meeus@gmail.com>,
	Eric Dumazet <erdnetdev@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: RE: TCP socket send return EAGAIN unexpectedly when sending small fragments
Date: Fri, 10 Jun 2022 15:21:30 +0000	[thread overview]
Message-ID: <0e02ea2593204cd9805c6ed4b7f46c98@AcuMS.aculab.com> (raw)
In-Reply-To: <CAMJ=MEdctBNSihixym1ZO9RVaCa_FpTQ8e4xFukz3eN8F1P8bQ@mail.gmail.com>

...
> If the 5 queued packets on the sending side would cause the EAGAIN
> issue, the real question maybe is why the receiving side is not
> sending the ACK within the 10ms while for earlier messages the ACK is
> sent much sooner.

Have you disabled Nagle (TCP_NODELAY) ?

Nagle only really works for bulk data transfer (large sends)
and interactive sessions (command - response).
For nearly everything else it adds unwanted 100ms delays.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2022-06-10 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 12:48 TCP socket send return EAGAIN unexpectedly when sending small fragments Ronny Meeus
2022-06-10 14:21 ` Eric Dumazet
2022-06-10 15:16   ` Ronny Meeus
2022-06-10 15:21     ` David Laight [this message]
2022-06-10 17:16       ` Ronny Meeus
2022-06-10 17:42         ` Willy Tarreau
2022-06-10 18:14           ` Ronny Meeus
2022-06-10 17:46     ` Eric Dumazet
2022-06-10 18:21       ` Ronny Meeus

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=0e02ea2593204cd9805c6ed4b7f46c98@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=erdnetdev@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ronny.meeus@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).