From: Eric Dumazet <eric.dumazet@gmail.com>
To: Erik Hugne <erik.hugne@ericsson.com>
Cc: sathya.perla@emulex.com, subbu.seetharaman@emulex.com,
ajit.khaparde@emulex.com, netdev@vger.kernel.org
Subject: Re: be2net: GRO for non-inet protocols
Date: Fri, 05 Apr 2013 08:28:22 -0700 [thread overview]
Message-ID: <1365175702.3405.2.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130405132007.GF7551@eerihug-hybrid.ki.sw.ericsson.se>
On Fri, 2013-04-05 at 15:20 +0200, Erik Hugne wrote:
> I'm adding GRO support for the TIPC protocol and
> tried to test it on a pair of HP G7 blades with
> Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01) NICs.
>
> However, my GRO callback is never invoked on this setup, and
> i suspect the be2net driver is to blame.
> I had a brief look at the driver, first suspecting that the
> do_gro check only passed for inet protocols (tcpf must be set
> in the be_rx_compl_info struct).
> However, removing this check did not change the behavior.
Try following instead :
diff --git a/drivers/net/ethernet/emulex/benet/be_main.c b/drivers/net/ethernet/emulex/benet/be_main.c
index 536afa2..1b9e467 100644
--- a/drivers/net/ethernet/emulex/benet/be_main.c
+++ b/drivers/net/ethernet/emulex/benet/be_main.c
@@ -1355,7 +1355,7 @@ static void skb_fill_rx_data(struct be_rx_obj *rxo, struct sk_buff *skb,
}
/* Process the RX completion indicated by rxcp when GRO is disabled */
-static void be_rx_compl_process(struct be_rx_obj *rxo,
+static void be_rx_compl_process(struct be_rx_obj *rxo, struct napi_struct *napi,
struct be_rx_compl_info *rxcp)
{
struct be_adapter *adapter = rxo->adapter;
@@ -1385,7 +1385,7 @@ static void be_rx_compl_process(struct be_rx_obj *rxo,
if (rxcp->vlanf)
__vlan_hwaccel_put_tag(skb, rxcp->vlan_tag);
- netif_receive_skb(skb);
+ napi_gro_receive(&napi, skb);
}
/* Process the RX completion indicated by rxcp when GRO is enabled */
@@ -2113,7 +2113,7 @@ static int be_process_rx(struct be_rx_obj *rxo, struct napi_struct *napi,
if (do_gro(rxcp))
be_rx_compl_process_gro(rxo, napi, rxcp);
else
- be_rx_compl_process(rxo, rxcp);
+ be_rx_compl_process(rxo, napi, rxcp);
loop_continue:
be_rx_stats_update(rxo, rxcp);
}
next prev parent reply other threads:[~2013-04-05 15:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 13:20 be2net: GRO for non-inet protocols Erik Hugne
2013-04-05 15:28 ` Eric Dumazet [this message]
2013-04-05 15:31 ` Eric Dumazet
2013-04-08 6:40 ` Erik Hugne
2013-04-08 15:24 ` Erik Hugne
2013-04-08 15:51 ` Eric Dumazet
2013-04-09 7:55 ` Erik Hugne
2013-04-09 13:44 ` Eric Dumazet
2013-04-09 14:22 ` Erik Hugne
2013-04-09 14:32 ` Eric Dumazet
2013-04-09 14:48 ` Erik Hugne
2013-04-09 14:31 ` Bandi,Sarveshwar
2013-04-09 16:31 ` Erik Hugne
2013-04-10 13:46 ` Bandi,Sarveshwar
2013-04-10 13:53 ` Erik Hugne
2013-04-24 7:44 ` Erik Hugne
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=1365175702.3405.2.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=ajit.khaparde@emulex.com \
--cc=erik.hugne@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@emulex.com \
--cc=subbu.seetharaman@emulex.com \
/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