All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ron Flory <ron.flory@adtran.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.6 & 2.4.7 networking performance: seeing serious delays  inTCP layer depending upon packet length
Date: Thu, 09 Aug 2001 13:59:00 -0500	[thread overview]
Message-ID: <3B72DD74.199F31B7@adtran.com> (raw)
In-Reply-To: <OF867C5EBC.F320CE04-ON87256AA3.00608124@boulder.ibm.com>

Shirley Ma wrote:
> 
> Hi, Ron,
> 
>      I am interested the problem you posted. I tried to reproduce
> this problem on my machine and failed. Would you please point your 
> programs to me, so I can reproduce this problem and do more 
> investigation? If not, please let me know whether it is reproducible,
> and please collect both client/server ethereal log.

 OK, will follow-on in a private email (to minimize lkml traffic)
 
 I can easily reproduce the problem by performing a socket 'write' as
two separate operations:

   write(sock, buf1..)
   write(sock, buf2..)

 If on the other hand I combine the buffers then issue a single
'write':

   write(sock, both_bufs...)

 the problem magically disappears (because the inter-block handshaking 
requirements change, which is where I think the problem actually lies).

 Since the problem is also present using the loopback device, both 
client/server sides would be present in a Ethereal long of LO.

 I would imagine anybody running a large Linux ftp/http server would be
interested in this...

ron

      reply	other threads:[~2001-08-09 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 17:46 Re:Kernel 2.4.6 & 2.4.7 networking performance: seeing serious delays in TCP layer depending upon packet length Shirley Ma
2001-08-09 18:59 ` Ron Flory [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=3B72DD74.199F31B7@adtran.com \
    --to=ron.flory@adtran.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.