From: Divy Le Ray <divy@chelsio•com>
To: Herbert Xu <herbert@gondor•apana.org.au>
Cc: "David S. Miller" <davem@davemloft•net>, netdev@vger•kernel.org
Subject: Re: [0/4] GRO optimisations
Date: Thu, 29 Jan 2009 16:28:57 -0800 [thread overview]
Message-ID: <498249C9.3050708@chelsio.com> (raw)
In-Reply-To: <20090130001849.GA1272@gondor.apana.org.au>
Herbert Xu wrote:
> Hi Dave:
>
> This is a dump of my current patches to optimise GRO in order
> to get cxgb3 performance back up to the LRO level. I've got
> some more ideas but I'd like to get this out first so it doesn't
> rot in my tree.
>
> Oh and of course a direct LRO comparison isn't exactly fair because
> LRO skipped some tests such as checking the IP header checksum
> (naughty :) so the current 5.7 vs. 6.1 figure isn't all that bad.
>
> But I think we should be able to get back to 6Gb/s with cxgb3
>
Hi Herbert,
I'll give these patches a try within a day or two.
Please note that the 6Gb/s rate is achieved on a low perf server.
Using this server makes it easy to witness the impact of optimizations.
Faster boxes reach line rate.
Just want to make clear that cxgb3 HW is not limited to 6Gb/s ;)
Cheers,
Divy
next prev parent reply other threads:[~2009-01-30 0:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 0:18 [0/4] GRO optimisations Herbert Xu
2009-01-30 0:19 ` [PATCH 1/4] gro: Move common completion code into helpers Herbert Xu
2009-01-30 0:19 ` [PATCH 2/4] gro: Avoid copying headers of unmerged packets Herbert Xu
2009-01-30 0:19 ` [PATCH 3/4] gro: Do not merge paged packets into frag_list Herbert Xu
2009-01-30 0:19 ` [PATCH 4/4] gro: Open-code memcpy in napi_fraginfo_skb Herbert Xu
2009-01-30 0:28 ` Divy Le Ray [this message]
2009-01-30 0:37 ` [0/4] GRO optimisations Rick Jones
2009-01-30 1:29 ` Herbert Xu
2009-01-30 0:54 ` David Miller
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=498249C9.3050708@chelsio.com \
--to=divy@chelsio$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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