From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org
Subject: Re: [0/4] GRO optimisations
Date: Thu, 29 Jan 2009 16:54:19 -0800 (PST) [thread overview]
Message-ID: <20090129.165419.104743020.davem@davemloft.net> (raw)
In-Reply-To: <20090130001849.GA1272@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Fri, 30 Jan 2009 11:18:49 +1100
> 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.
All applied to net-next-2.6, thanks Herbert!
prev parent reply other threads:[~2009-01-30 0:54 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 ` [0/4] GRO optimisations Divy Le Ray
2009-01-30 0:37 ` Rick Jones
2009-01-30 1:29 ` Herbert Xu
2009-01-30 0:54 ` David Miller [this message]
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=20090129.165419.104743020.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
/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).