netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: peter.p.waskiewicz.jr@intel.com, netdev@vger.kernel.org
Subject: Re: Question on TSO maximum segment sizes.
Date: Thu, 11 Oct 2007 16:50:46 -0700	[thread overview]
Message-ID: <470EB6D6.9020704@hp.com> (raw)
In-Reply-To: <20071011.163737.36654032.davem@davemloft.net>

David Miller wrote:
> From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
> Date: Thu, 11 Oct 2007 16:27:14 -0700
> 
> 
>>I'm having an issue with TSO right vs. hardware that can't take the
>>maximum segment size sent from the stack.  I've been told that the
>>maximum packet size that can be sent to the hardware today is 64k, but
>>my hardware can only take 32k in certain modes per queue due to hardware
>>limitations. 

Bletch.

>> I have two questions regarding this: 1) where is this
>>value set in the TCP code, and 2) Is this something that can be
>>configured on the fly?  If the answer to 2 is no, I will try and put
>>something together to allow this to happen.
> 
> 
> The TCP code just builds the maximum possible for the underlying
> protocol, be it ipv4 or ipv6.  It takes the underlying protocol
> maximum packet length, subtracts the amount of header space it
> knows will be used, and uses that.
> 
> You'll need to use GSO sw segmentation to split the TSO packets
> which are too big for your HW to handle.

For just messing about, might it be possible to tweak the socket buffer sizes 
and tcp_tso_win_divisor to kludge things for a short while?  Couldn't ship that 
way certainly, but assuming Peter's going to get his broken hardware fixed it 
might let him limp along until then.

rick jones

  reply	other threads:[~2007-10-11 23:56 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 [this message]
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

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=470EB6D6.9020704@hp.com \
    --to=rick.jones2@hp.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.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).