public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH net-next-2.6] gro: __napi_gro_receive() optimizations
Date: Thu, 26 Aug 2010 11:03:54 +0200	[thread overview]
Message-ID: <1282813434.2476.200.camel@edumazet-laptop> (raw)
In-Reply-To: <20100826.005139.183034040.davem@davemloft.net>

Le jeudi 26 août 2010 à 00:51 -0700, David Miller a écrit :
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Wed, 25 Aug 2010 23:15:11 +0200
> 
> > Yes, we can inline it, this will speedup the non vlan case as well :)
> 
> Agreed.
> 
> But I believe you can find a better place to put __napi_gro_receive()
> than etherdevice.h, even though yes it does have a hard dependency on
> that thing. :-)
> 

I tried but failed :(

Or move __napi_gro_receive() in a new header,
because etherdevice.h needs to include netdevice.h

(is_etherdev_addr(), dev_hw_addr_random())



  reply	other threads:[~2010-08-26  9:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 20:33 [PATCH net-next-2.6] gro: __napi_gro_receive() optimizations Eric Dumazet
2010-08-25 20:45 ` Stephen Hemminger
2010-08-25 20:54   ` Eric Dumazet
2010-08-25 20:57 ` David Miller
2010-08-25 21:15   ` Eric Dumazet
2010-08-26  7:51     ` David Miller
2010-08-26  9:03       ` Eric Dumazet [this message]
2010-08-27  4:35     ` [PATCH net-next-2.6 v3] " Eric Dumazet
2010-08-27  4:38       ` David Miller
2010-08-27  4:42         ` Herbert Xu
2010-08-27  5:02           ` David Miller
2010-08-27  4:43         ` Eric Dumazet
2010-08-27  5:01           ` David Miller
2010-08-27  5:01         ` [PATCH net-next-2.6 v4] " Eric Dumazet
2010-08-27  5:03           ` 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=1282813434.2476.200.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=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