All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ravinandan Arakali" <ravinandan.arakali@neterion.com>
To: "'David Miller'" <davem@davemloft.net>, <mchan@broadcom.com>
Cc: <herbert@gondor.apana.org.au>, <netdev@vger.kernel.org>
Subject: RE: [PATCH]NET: Add ECN support for TSO
Date: Tue, 11 Jul 2006 18:45:48 -0700	[thread overview]
Message-ID: <002201c6a554$e6af4580$4710100a@pc.s2io.com> (raw)
In-Reply-To: <20060708.133223.35527292.davem@davemloft.net>

Michael/David,
Thanks for the comments on LRO. The current LRO code in S2io driver is not
aware of ECN. While I was trying to fix this, the first thing I encountered
was to check, in the driver, if ECN is enabled for current session. To do
this, I try to get hold of the socket by doing something like:

tk = tcp_sk(skb->sk);
if (tk->ecn_flags & TCP_ECN_OK)
   /* Check CE, ECE, CWR etc */

I find that skb->sk is NULL. Is this the correct way to check the
per-session
ECN capability ? Why is skb->sk NULL ?

Thanks,
Ravi

-----Original Message-----
From: David Miller [mailto:davem@davemloft.net]
Sent: Saturday, July 08, 2006 1:32 PM
To: mchan@broadcom.com
Cc: ravinandan.arakali@neterion.com; herbert@gondor.apana.org.au;
netdev@vger.kernel.org
Subject: Re: [PATCH]NET: Add ECN support for TSO


From: "Michael Chan" <mchan@broadcom.com>
Date: Fri, 7 Jul 2006 18:01:34 -0700

> However, Large Receive Offload will be a different story.  If
> packets are accumulated in the hardware and presented to the stack
> as one large packet, the stack will not be able to calculate the
> cumulative NS correctly.  Unless the hardware calculates the partial
> NS over the LRO packet and puts it in the SKB when handing over the
> packet.

This is correct, LRO hardware would need to do something to make sure
the nonce parity works out.


  reply	other threads:[~2006-07-12  1:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08  1:01 [PATCH]NET: Add ECN support for TSO Michael Chan
2006-07-08 20:32 ` David Miller
2006-07-12  1:45   ` Ravinandan Arakali [this message]
2006-07-12  1:51     ` David Miller
2006-07-13 17:26   ` Ravinandan Arakali
  -- strict thread matches above, loose matches on Subject: below --
2006-07-14 16:12 Dan Reader
2006-07-26 19:40 ` Michael Chan
2006-07-13 19:35 Michael Chan
2006-07-14  5:03 ` David Miller
2006-07-12  4:53 Michael Chan
2006-07-12  6:11 ` David Miller
2006-07-12 17:15   ` Ravinandan Arakali
2006-07-07 20:57 Michael Chan
2006-07-07 21:59 ` David Miller
2006-07-07 22:52   ` David Miller
2006-06-28  3:06 Michael Chan
2006-06-28  3:10 ` Herbert Xu
2006-06-28  3:40   ` Michael Chan
2006-06-28  3:48     ` Herbert Xu
2006-06-28  4:37       ` Michael Chan
2006-06-28  4:42         ` Herbert Xu
2006-06-28  4:54           ` Michael Chan
2006-06-28  4:57             ` Herbert Xu
2006-06-29 19:30         ` David Miller
2006-07-07 18:56 ` Ravinandan Arakali

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='002201c6a554$e6af4580$4710100a@pc.s2io.com' \
    --to=ravinandan.arakali@neterion.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=mchan@broadcom.com \
    --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.