From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: dhananjay.phadke@qlogic.com, 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 17:33:38 -0800 [thread overview]
Message-ID: <4B43E872.5000809@hp.com> (raw)
In-Reply-To: <20100105.163343.14826539.davem@davemloft.net>
David Miller wrote:
> From: Dhananjay Phadke <dhananjay.phadke@qlogic.com>
> Date: Tue, 5 Jan 2010 15:55:10 -0800
>
>
>>The LRO you are talking about was still kernel based
>>LRO. Even GRO doesn't save PCIe transactions as much
>>HW LRO does. That is the key. The difference between
>>HW LRO and GRO is significant to keep former alive
>>for a while.
Is it really the PCIe transactions (*)? ISTR that HW LRO also tended to
significantly cut-down on the ACK rate, rather like the oft-derided ACK
avoidance heuristics in Solaris, HP-UX and various MacOSX revs.
rick jones
* OK, I am recalling that long ago and far away, the Alteon AceNIC (PCI) had
very high DMA setup times - so long that if an outbound (in this case) packet
was more than 1.something buffers the card was unable to acheive link-rate with
a 1500 byte MTU. It meant that for straight copy outbound was fine, but for
copy avoided (eg sendfile() - this was HP-UX 11) one was sub-par because it was
at least two buffers per packet - aka two DMA setups - and sometimes three. One
workaround was to use JumboFrames - the larger MTU helped.
>
>
> 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.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-06 1:33 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 [this message]
2010-01-06 3:57 ` David Miller
2010-01-06 1:56 ` Dhananjay Phadke
2010-01-06 3:51 ` David Miller
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=4B43E872.5000809@hp.com \
--to=rick.jones2@hp.com \
--cc=amit.salecha@qlogic.com \
--cc=davem@davemloft.net \
--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).