From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: LRO/GRO and libpcap packet reordering Date: Fri, 15 Mar 2013 00:16:20 +0100 Message-ID: <1363302980.29475.45.camel@edumazet-glaptop> References: <1363298294.2695.15.camel@bwh-desktop.uk.solarflarecom.com> <1363301695.29475.38.camel@edumazet-glaptop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Ben Hutchings , Network Development To: Andy Lutomirski Return-path: Received: from mail-ee0-f41.google.com ([74.125.83.41]:45476 "EHLO mail-ee0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753285Ab3CNXQY (ORCPT ); Thu, 14 Mar 2013 19:16:24 -0400 Received: by mail-ee0-f41.google.com with SMTP id c13so1361011eek.28 for ; Thu, 14 Mar 2013 16:16:23 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 2013-03-14 at 15:58 -0700, Andy Lutomirski wrote: > Right. This is the part that I'm wondering about an efficient fix to > (i.e. flush GRO state for one flow whenever a packet for the reversed > flow is seen). It doesnt seem doable easily, because network header and tcp headers are handled in two separate functions in GRO stack (inet_gro_receive() & tcp_gro_receive() What you could do is changing MAX_GRO_SKBS from 8 to 1 (basically allowing only one flow in GRO stack)