netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Yasevich <vyasevich@gmail.com>
To: David Miller <davem@davemloft.net>, jbaron@akamai.com
Cc: netdev@vger.kernel.org, kaber@trash.net
Subject: Re: macvlan: optimizing the receive path?
Date: Mon, 06 Oct 2014 09:04:45 -0400	[thread overview]
Message-ID: <5432936D.7010906@gmail.com> (raw)
In-Reply-To: <20141004.204203.2211720828886085354.davem@davemloft.net>

On 10/04/2014 08:42 PM, David Miller wrote:
> From: Jason Baron <jbaron@akamai.com>
> Date: Thu, 02 Oct 2014 16:28:13 -0400
> 
>> --- a/drivers/net/macvlan.c
>> +++ b/drivers/net/macvlan.c
>> @@ -321,8 +321,8 @@ static rx_handler_result_t macvlan_handle_frame(struct sk_buff **pskb)
>>         skb->dev = dev;
>>         skb->pkt_type = PACKET_HOST;
>>  
>> -       ret = netif_rx(skb);
>> -
>> +      macvlan_count_rx(vlan, len, true, 0);
>> +      return RX_HANDLER_ANOTHER;
>>  out:
>>         macvlan_count_rx(vlan, len, ret == NET_RX_SUCCESS, 0);
>>         return RX_HANDLER_CONSUMED;
> 
> That last argument to macvlan_count_rx() is a bool and thus should be
> specified as "false".  Yes I know other areas of this file get it
> wrong too.
> 
> Also, what about GRO?  Won't we get GRO processing if we do this via
> netif_rx() but not via the RX_HANDLER_ANOTHER route?  Just curious...

Wouldn't GRO already happen at the lower level?  For macvlan-to-macvlan,
you'd typically have large packets so no need for GRO.

-vlad

  reply	other threads:[~2014-10-06 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 20:28 macvlan: optimizing the receive path? Jason Baron
2014-10-02 21:31 ` Stephen Hemminger
2014-10-03 15:08   ` Jason Baron
2014-10-03 16:16 ` Vlad Yasevich
2014-10-05  0:42 ` David Miller
2014-10-06 13:04   ` Vlad Yasevich [this message]
2014-10-07 17:35     ` Jason Baron
2014-10-07 18:00       ` Eric Dumazet
2014-10-07 18:49       ` 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=5432936D.7010906@gmail.com \
    --to=vyasevich@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jbaron@akamai.com \
    --cc=kaber@trash.net \
    --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).