DPDK usage discussions
 help / color / mirror / Atom feed
From: JieSong <songj@zctt.com>
To: "Ido Goshen" <Ido@cgstowernetworks.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Is it possible to receive packets with bad CRC?
Date: Tue, 8 Jun 2021 11:44:10 +0800	[thread overview]
Message-ID: <tencent_4691A2EE757D967406C3D0FD@qq.com> (raw)
In-Reply-To: <DB7PR09MB23453F55767C3065C8979746D6C80@DB7PR09MB2345.eurprd09.prod.outlook.com>

Hi Ido,
&nbsp; &nbsp; I have the same question as yours, I want to get all the packets even the CRC/FCS error packet.
&nbsp; &nbsp; Without DPDK I set the nic with "ethtool -K rx-all on", Then i can tcpdump all the packets both good and error packets.
&nbsp; &nbsp; But I have no ideal with DPDK. Did you find something for this question?&nbsp;


Thanks


Jie



&nbsp;
&nbsp;
&nbsp;
------------------&nbsp;Original&nbsp;------------------
From: &nbsp;"Ido Goshen"<Ido@cgstowernetworks.com&gt;;
Date: &nbsp;Mon, Dec 14, 2020 00:56 AM
To: &nbsp;"users@dpdk.org"<users@dpdk.org&gt;; 

Subject: &nbsp;[dpdk-users] Is it possible to receive packets with bad CRC?

&nbsp;

Hi

By default bad CRC packets are dropped and raise the ierror counter.

Is there a way to change this behavior for I350 (igb) and rx it by the app?

I’ve tried setting DEV_RX_OFFLOAD_KEEP_CRC but this doesn’t help (I think this only keeps CRC for good packets)
I’ve also tried enabling the Store Bad Packet (not sure what it does but it’s the closet I could find) by setting in e1000/igb_rxtx.c
rctl |= E1000_RCTL_SBP;&nbsp; E1000_WRITE_REG(hw, E1000_RCTL, rctl);
Didn’t help either.

Is it possible to do with I350?
Or with any of the other intel NICs? X522 (ixgbe) or X710 (i40e)?

Thanx,

&nbsp; *&nbsp;&nbsp; Ido

  reply	other threads:[~2021-06-08  3:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-13 16:55 Ido Goshen
2021-06-08  3:44 ` JieSong [this message]
2021-06-08 15:23   ` Stephen Hemminger
2021-06-09  4:58     ` songj

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=tencent_4691A2EE757D967406C3D0FD@qq.com \
    --to=songj@zctt.com \
    --cc=Ido@cgstowernetworks.com \
    --cc=users@dpdk.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).