From: Eric Dumazet <eric.dumazet@gmail.com>
To: "\"Oleg A. Arkhangelsky\"" <sysoleg@yandex.ru>
Cc: Amit Salecha <amit.salecha@qlogic.com>, netdev@vger.kernel.org
Subject: Re: [PATCH NEXT 3/5] qlcnic: vlan lro support
Date: Fri, 17 Sep 2010 10:28:26 +0200 [thread overview]
Message-ID: <1284712107.3391.32.camel@edumazet-laptop> (raw)
In-Reply-To: <381611284708887@web110.yandex.ru>
Le vendredi 17 septembre 2010 à 11:34 +0400, "Oleg A. Arkhangelsky" a
écrit :
>
> 17.09.2010, 11:10, "Amit Salecha" <amit.salecha@qlogic.com>:
> >> -----Original Message-----
> >> From: Eric Dumazet [mailto:eric.dumazet@gmail.com]
> >> Sent: Thursday, September 16, 2010 6:57 PM
> >> To: Amit Salecha
> >> Cc: davem@davemloft.net; netdev@vger.kernel.org; Ameen Rahman; Anirban
> >> Chakraborty
> >> Subject: Re: [PATCH NEXT 3/5] qlcnic: vlan lro support
> >>
> >> Le jeudi 16 septembre 2010 à 06:14 -0700, Amit Kumar Salecha a écrit :
> >>> LRO + GRO + vlan rx accleration support, performance increases
> >>> around 20% and cpu utilization reduces around 70% on vlan interface.
> >> Interesting. What is the workload that demonstrates such gains ?
> >
> > Just to demonstrate decrease in cpu utilization further:
> > I have taken numbers with various load. I used iperf application to run tcp traffic on vlan interface.
>
> > There is around 80-90% of reduction in cpu utilization.
>
> I'm wondering, how can this scale further. For example if I have 200K low speed simultaneous
> TCP connections (router appliance case with many users). Can GRO give us some gain here?
>
I dont think it can help in a mixed trafic:
GRO in itself has an overhead and cannot handle more than 8 different
sessions per NAPI run.
UDP frames hit the overhead but not the GRO gain.
Because most tcp sessions are short lived and initcwnd is small, most
frames wont be coalesced.
next prev parent reply other threads:[~2010-09-17 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 13:14 [PATCH NEXT 0/5]qlcnic: vlan rx accleration support Amit Kumar Salecha
2010-09-16 13:14 ` [PATCH NEXT 1/5] qlcnic: support vlan rx accleration Amit Kumar Salecha
2010-09-16 13:26 ` Eric Dumazet
2010-09-16 13:36 ` Eric Dumazet
2010-09-16 13:14 ` [PATCH NEXT 2/5] qlcnic: vlan gro support Amit Kumar Salecha
2010-09-16 13:14 ` [PATCH NEXT 3/5] qlcnic: vlan lro support Amit Kumar Salecha
2010-09-16 13:27 ` Eric Dumazet
2010-09-16 18:13 ` Amit Salecha
2010-09-17 7:10 ` Amit Salecha
2010-09-17 7:34 ` "Oleg A. Arkhangelsky"
2010-09-17 8:28 ` Eric Dumazet [this message]
2010-09-16 13:14 ` [PATCH NEXT 4/5] qlcnic: remove fw version check Amit Kumar Salecha
2010-09-16 13:14 ` [PATCH NEXT 5/5] qlcnic: update version 5.0.10 Amit Kumar Salecha
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=1284712107.3391.32.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=amit.salecha@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=sysoleg@yandex.ru \
/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