public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Hugne <erik.hugne@ericsson.com>
To: "Bandi,Sarveshwar" <Sarveshwar.Bandi@Emulex.Com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	"Perla, Sathya" <Sathya.Perla@Emulex.Com>,
	"Seetharaman, Subramanian" <subbu.seetharaman@emulex.com>,
	"Khaparde, Ajit" <Ajit.Khaparde@Emulex.Com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: be2net: GRO for non-inet protocols
Date: Wed, 10 Apr 2013 15:53:37 +0200	[thread overview]
Message-ID: <20130410135337.GD7147@eerihug-hybrid.ki.sw.ericsson.se> (raw)
In-Reply-To: <9982e479-7a8c-4520-999b-9fb59dc62689@CMEXHTCAS2.ad.emulex.com>

On Wed, Apr 10, 2013 at 01:46:53PM +0000, Bandi,Sarveshwar wrote:
> Can you check if packets are garbled when using netif_receive_skb?
> Or it happens only when napi_gro_receive is used?

Yes, all received packets are OK when netif_receive_skb is used.
It's only when napi_gro_receive is used (from the context of be_rx_compl_process,
as per Eric's patch) that i get the corrupted packets.

//E

  reply	other threads:[~2013-04-10 13:58 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
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 [this message]
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=20130410135337.GD7147@eerihug-hybrid.ki.sw.ericsson.se \
    --to=erik.hugne@ericsson.com \
    --cc=Ajit.Khaparde@Emulex.Com \
    --cc=Sarveshwar.Bandi@Emulex.Com \
    --cc=Sathya.Perla@Emulex.Com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --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