From: "David S. Miller" <davem@davemloft.net>
To: John Heffner <jheffner@psc.edu>
Cc: netdev@oss.sgi.com
Subject: Re: TSO and MSS
Date: Wed, 29 Sep 2004 15:46:45 -0700 [thread overview]
Message-ID: <20040929154645.4e8987d2.davem@davemloft.net> (raw)
In-Reply-To: <Pine.NEB.4.33.0409291830440.3434-100000@dexter.psc.edu>
On Wed, 29 Sep 2004 18:38:52 -0400 (EDT)
John Heffner <jheffner@psc.edu> wrote:
> net/ipv4/ip_output.c:ip_queue_xmit():
>
> mtu = dst_pmtu(&rt->u.dst);
> if (skb->len > mtu && (sk->sk_route_caps & NETIF_F_TSO)) {
> unsigned int hlen;
>
> /* Hack zone: all this must be done by TCP. */
> hlen = ((skb->h.raw - skb->data) + (skb->h.th->doff << 2));
> skb_shinfo(skb)->tso_size = mtu - hlen;
> skb_shinfo(skb)->tso_segs =
> (skb->len - hlen + skb_shinfo(skb)->tso_size - 1)/
> skb_shinfo(skb)->tso_size - 1;
> }
>
> Does the "Hack zone" comment indicate this case has already been
> considered?
The "Hack zone" comment is saying that we should be doing this
work in tcp_transmit_skb() but cannot because ip_queue_xmit()
is where a route is hooked up if sk->sk_dst_cache is NULL.
If you are on ethernet using different MTU's, shouldn't you be
getting ICMP messages back when trying to communicate with that
host which will decrease the PMTU of the path? TCP's MSS is
determined in terms of this, so I can't see what the issue is.
Note I would like to move this "Hack zone" code up into tcp_transmit_skb()
for another reason, it would make the TSO stuff in tcp_skb_cb[] redundant.
next prev parent reply other threads:[~2004-09-29 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 22:38 TSO and MSS John Heffner
2004-09-29 22:46 ` David S. Miller [this message]
2004-09-29 22:51 ` John Heffner
2004-10-01 4:18 ` David S. Miller
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=20040929154645.4e8987d2.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jheffner@psc.edu \
--cc=netdev@oss.sgi.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).