All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: John Heffner <jheffner@psc.edu>
Cc: netdev@vger.kernel.org
Subject: Re: Question on TSO maximum segment sizes.
Date: Thu, 11 Oct 2007 18:29:51 -0700	[thread overview]
Message-ID: <470ECE0F.4060506@candelatech.com> (raw)
In-Reply-To: <470ECC71.1070303@psc.edu>

John Heffner wrote:
> Ben Greear wrote:
>> I just tried turning off my explicit SO_SNDBUF/SO_RCVBUG settings in 
>> my app,
>> and the connection ran very poorly through a link with even a small
>> bit of latency (~2-4ms I believe).
> 
> I often run at full gigabit or faster with latencies of 100+ ms.  Can 
> you give a bit more detail?

I'm doing non-blocking TCP sends, write sizes of around 64k, and I'm
doing this to/from the same system with the send-to-self patch.
I am running full-duplex (930+Mbps tx + rx on both ports)
(this is about 980Mbps on the wire).

If I don't set the tx-queue % rx-queue sizes large (~4MB), it does not
perform well when running through my latency emulator.

If I do set them, then it runs just fine (barring an occassional
TCP throughput deadlock & ACK storm that is being worked on separately.)

If it works for other people, then it could be something else
weird about my setup.  I have an easy work-around (been in the
code for years and years now), so I'm not too worried either way.

Thanks,
Ben

> 
>   -John


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2007-10-12  1:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 23:27 Question on TSO maximum segment sizes Waskiewicz Jr, Peter P
2007-10-11 23:37 ` David Miller
2007-10-11 23:50   ` Rick Jones
2007-10-12  0:02     ` David Miller
2007-10-12  0:06       ` Waskiewicz Jr, Peter P
2007-10-12  0:17         ` Ben Greear
2007-10-12  0:22           ` David Miller
2007-10-12  1:22           ` John Heffner
2007-10-12  1:29             ` Ben Greear [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=470ECE0F.4060506@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=jheffner@psc.edu \
    --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 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.