netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Gallatin <gallatin@myri.com>
To: David Miller <davem@davemloft.net>
Cc: ossthema@de.ibm.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, tklein@de.ibm.com,
	raisch@de.ibm.com, jb.billaud@gmail.com, hering2@de.ibm.com
Subject: Re: [PATCH] lro: IP fragment checking
Date: Mon, 01 Dec 2008 19:19:01 -0500	[thread overview]
Message-ID: <49347EF5.2010206@myri.com> (raw)
In-Reply-To: <20081201.160722.114600830.davem@davemloft.net>

David Miller wrote:
> From: Andrew Gallatin <gallatin@myri.com>
> Date: Mon, 01 Dec 2008 16:53:14 -0500
> 
>> What hardware does an explicit check for fragmentation?
> 
> If the packet is fragmented, the chip shouldn't even be
> looking at the ports to make LRO deferral decisions let
> alone pass it down as a LRO'able frame.

You seem to be assuming that all consumers of the Linux LRO
interface have support for LRO in hardware.  Many (most?)
do not.  The way software LRO works in these drivers is the
driver just sends all packets through lro_receive_skb() when
LRO is configured and enabled.  The LRO layer then filters
out things which are not eligible for LRO.  See, for example,
igb_receive_skb().

If you're arguing that the hardware should have checked for
fragmentation, then many (most?) things in lro_tcp_ip_check()
should be removed.  They are all basic sanity checks for
packets that would not be considered for LRO by a hardware
implementation, but are required by a software implementation
where all packets are through the LRO code.

Drew

      reply	other threads:[~2008-12-02  0:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01  8:58 [PATCH] lro: IP fragment checking Jan-Bernd Themann
2008-12-01  9:41 ` David Miller
2008-12-01 17:50 ` Andrew Gallatin
2008-12-01 21:18   ` David Miller
2008-12-01 21:53     ` Andrew Gallatin
2008-12-01 22:09       ` Ben Hutchings
2008-12-02  0:02         ` Andrew Gallatin
2008-12-02  0:18           ` Ben Hutchings
2008-12-02 14:42             ` Andrew Gallatin
2008-12-02 15:18               ` Ben Hutchings
2008-12-02 15:36                 ` Andrew Gallatin
2008-12-02  0:07       ` David Miller
2008-12-02  0:19         ` Andrew Gallatin [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=49347EF5.2010206@myri.com \
    --to=gallatin@myri.com \
    --cc=davem@davemloft.net \
    --cc=hering2@de.ibm.com \
    --cc=jb.billaud@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ossthema@de.ibm.com \
    --cc=raisch@de.ibm.com \
    --cc=tklein@de.ibm.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).