Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "ツ Leandro Melo de Sales" <leandroal@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: TCP packet size and delivery packet decisions
Date: Tue, 07 Sep 2010 06:36:59 +0200	[thread overview]
Message-ID: <1283834219.2585.455.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTike9biiUvAhckJKHCB6dyS4PzHgFFPF5RNEw4PP@mail.gmail.com>

Le mardi 07 septembre 2010 à 01:20 -0300, ツ Leandro Melo de Sales a
écrit :
> Hi all,
>    We are facing a not expected behavior (at least for us) from the
> TCP stack under Linux. We need to write 78 bytes per writing using
> write() function. But instead of sending 78 bytes TCP implementation
> in Linux sends 48 bytes and later 30 bytes. We then started to debug
> the implementation, but although we got some progress on this, I have
> decided to ask in this list if someone can anticipate provide me more
> information why TCP is not sending 78 at once, in addition to have any
> clarification about if it is possible to force TCP sends 78 bytes in
> each write() function call.
>    I have tried many alternatives: set TCP_CORK; used socket API to
> write a fixed 78 bytes per write() function call; and so forth). Also,
> I know that TCP is a byte-stream protocol and this decision is made by
> many different factors, such as cwd size, mss and so forth, but 78
> bytes is too small to split it in two different packets. Our
> application works as expected under Windows, it sends 78 bytes at
> once.
> 
>    In this way, any comment from the list regarding this issue will be
> kindly accepted and helpful.


Could you send a tcpdump of such session, with say first 10 packets ?




  reply	other threads:[~2010-09-07  4:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=_heUejVf-wmEcKd910gVtpD7Hr=cZ_cs2Q8n9@mail.gmail.com>
2010-09-07  4:20 ` TCP packet size and delivery packet decisions ツ Leandro Melo de Sales
2010-09-07  4:36   ` Eric Dumazet [this message]
2010-09-07  5:13     ` ツ Leandro Melo de Sales
2010-09-07  5:16       ` David Miller
2010-09-07  5:21         ` ツ Leandro Melo de Sales
2010-09-07  5:30           ` David Miller
2010-09-07  6:02             ` ツ Leandro Melo de Sales
2010-09-07  6:09               ` Eric Dumazet
2010-09-07  7:16                 ` ツ Leandro Melo de Sales
2010-09-07  7:32                   ` Eric Dumazet
2010-09-08 14:01                     ` ツ Leandro Melo de Sales
2010-09-07 11:39             ` Eric Dumazet
2010-09-07 12:15               ` Ilpo Järvinen
2010-09-08  3:18                 ` David Miller
2010-09-08 12:14                   ` Alexey Kuznetsov
2010-09-13  1:23                     ` David Miller
2010-09-14  9:37                       ` Alexey Kuznetsov
2010-09-15 17:29                         ` David Miller
2010-09-07 16:35               ` David Miller
2010-09-07 16:57               ` Rick Jones
2010-09-08 14:06               ` ツ Leandro Melo de Sales
2010-09-08 15:24                 ` David Miller
2010-09-08 16:03                   ` ツ Leandro Melo de Sales

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=1283834219.2585.455.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=leandroal@gmail.com \
    --cc=netdev@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