From: David Miller <davem@davemloft.net>
To: dhananjay.phadke@qlogic.com
Cc: shemminger@vyatta.com, amit.salecha@qlogic.com, netdev@vger.kernel.org
Subject: Re: [PATCH NEXT 0/2] qlcnic: Add Qlogic 1/10Gb Ethernet driver for CNA devices
Date: Tue, 05 Jan 2010 19:51:56 -0800 (PST) [thread overview]
Message-ID: <20100105.195156.39644124.davem@davemloft.net> (raw)
In-Reply-To: <7608421F3572AB4292BB2532AE89D5658B0BAE949E@AVEXMB1.qlogic.org>
From: Dhananjay Phadke <dhananjay.phadke@qlogic.com>
Date: Tue, 5 Jan 2010 17:56:00 -0800
>> But HW LRO is not bridge/forwarding/etc. agnostic because it loses
>> information.
>>
>> As soon as I turn on forwarding to make a NAT box or whatever, all of
>> the hw LRO gets turned off and we're back to square one for local
>> connections on the machine.
>
> I won't defend other vendors' implementation. Even if LRO was
> not turned off for bridge/forwarding, we still wouldn't accumulate
> those remote flows because the dest IP address is not configured in
> firmware in our case. This is the reason why we have a inet
> notification listener (to tell firmware about local addresses).
Ok, but you do realize that because GRO maintains enough state
we can reconstitute packets across forwarding and bridging
thus decreasing the per-packet costs in those situations as
well right?
That's why hardware vendors should strive to align their hw
LRO implementations with what GRO does, since it is truly
generic and allows to optimize all cases not just local
TCP streams.
next prev parent reply other threads:[~2010-01-06 3:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 13:24 [PATCH NEXT 0/2] qlcnic: Add Qlogic 1/10Gb Ethernet driver for CNA devices Amit Kumar Salecha
2010-01-05 13:24 ` [PATCH NEXT 1/2] NET: Add Ethernet driver for QLOGIC " Amit Kumar Salecha
2010-01-05 13:24 ` [PATCH NEXT 2/2] qlcnic: Qlogic ethernet driver for " Amit Kumar Salecha
2010-01-05 17:08 ` Stephen Hemminger
2010-01-05 17:12 ` Stephen Hemminger
2010-01-05 17:07 ` [PATCH NEXT 0/2] qlcnic: Add Qlogic 1/10Gb Ethernet " Stephen Hemminger
2010-01-05 20:39 ` David Miller
2010-01-06 2:24 ` Amit Salecha
2010-01-06 2:36 ` Stephen Hemminger
2010-01-06 3:53 ` David Miller
2010-01-05 17:15 ` Stephen Hemminger
2010-01-05 18:40 ` Dhananjay Phadke
2010-01-05 18:45 ` Stephen Hemminger
2010-01-05 19:02 ` Dhananjay Phadke
2010-01-05 20:38 ` David Miller
2010-01-05 22:01 ` Dhananjay Phadke
2010-01-05 23:49 ` David Miller
2010-01-05 23:55 ` Dhananjay Phadke
2010-01-06 0:33 ` David Miller
2010-01-06 1:33 ` Rick Jones
2010-01-06 3:57 ` David Miller
2010-01-06 1:56 ` Dhananjay Phadke
2010-01-06 3:51 ` David Miller [this message]
2010-01-06 4:27 ` Dhananjay Phadke
2010-01-06 4:40 ` David Miller
2010-01-06 2:19 ` Dhananjay Phadke
2010-01-05 23:43 ` Ben Hutchings
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=20100105.195156.39644124.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amit.salecha@qlogic.com \
--cc=dhananjay.phadke@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).