From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH] lro: IP fragment checking
Date: Mon, 01 Dec 2008 16:07:22 -0800 (PST)
Message-ID: <20081201.160722.114600830.davem@davemloft.net>
References: <493423D7.5030203@myri.com>
	<20081201.131810.158631503.davem@davemloft.net>
	<49345CCA.1030209@myri.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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
To: gallatin@myri.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:55273
	"EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK)
	by vger.kernel.org with ESMTP id S1751068AbYLBAHZ (ORCPT
	<rfc822;netdev@vger.kernel.org>); Mon, 1 Dec 2008 19:07:25 -0500
In-Reply-To: <49345CCA.1030209@myri.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

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.