netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Radha Mohan <radhamohan_ch@yahoo.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>
Subject: Re: behavior of TSO in kernel
Date: Mon, 29 Jun 2009 12:14:55 +0530 (IST)	[thread overview]
Message-ID: <974032.57711.qm@web94813.mail.in2.yahoo.com> (raw)


David,

I think we do not need to do this when TSO is enabled.

At line 1562 in tcp_output.c (in tcp_write_xmit() function)

    if (tso_segs > 1 && !tcp_urg_mode(tp))
           limit = tcp_mss_split_point(sk, skb, mss_now,
                                            cwnd_quota);
    if (skb->len > limit &&
                    unlikely(tso_fragment(sk, skb, limit, mss_now)))

Since the hardware can split and send the packet, there is 
no need for this in software.

Am I missing something here?

-- Mohan



----- Original Message ----
From: Radha Mohan <radhamohan_ch@yahoo.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>
Sent: Saturday, 6 June, 2009 7:41:21 PM
Subject: Re: behavior of TSO in kernel


>The TSO engine of the networking has been rewritten at least
>3 times since 2.6.15
Thank you for the info.
Actually we are working on an SoC and we just started moving from kernel 2.6.15, so can you tell me from which kernel version the latest TSO engine is being used. That'll make our life easier and avoid moving kernels frequently. Currently we are thinking of moving to 2.6.24. Will that do??


      ICC World Twenty20 England &#39;09 exclusively on YAHOO! CRICKET http://cricket.yahoo.com


             reply	other threads:[~2009-06-29  6:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29  6:44 Radha Mohan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-05 14:39 behavior of TSO in kernel Radha Mohan
2009-06-06  1:20 ` David Miller
2009-06-06 14:11   ` Radha Mohan
2009-06-09  8:01     ` Ilpo Järvinen

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=974032.57711.qm@web94813.mail.in2.yahoo.com \
    --to=radhamohan_ch@yahoo.com \
    --cc=davem@davemloft.net \
    --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;
as well as URLs for NNTP newsgroup(s).