From: Yaron Illouz <yaroni@radcom.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: crc stripping for vf on same pf
Date: Thu, 15 Aug 2024 09:13:51 +0000 [thread overview]
Message-ID: <AM9PR09MB4995C20A2CDC990F344079B1A1802@AM9PR09MB4995.eurprd09.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
I have 2 pods running on same worker
Pod1 send to pod2
Pod2 receive with 4 bytes less at end of packet
This problem happens only if the 2 nic are on the same pf,
If different pf, the problem doesn’t occurs
I tried with dpdk21 and dpdk22
The code is using driver net_iavf
nic e810c
driver: ice
firmware-version: 4.00 0x800139bc 21.5.9
Who does the stripping? The dpdk code or the card?
Why is is different behavior for same pf and different pf ?
What should i change or check?
port_conf.rxmode.offloads |= RTE_ETH_RX_OFFLOAD_KEEP_CRC; //Don't strip CRC
port_conf.rxmode.offloads &= pi_devInfo.rx_offload_capa;
int ret = rte_eth_dev_configure(pi_nPort, nRxQueues, nTxQueues, &port_conf);
struct rte_eth_rxconf rx_conf;
rx_conf.offloads = RTE_ETH_RX_OFFLOAD_KEEP_CRC;
int ret = rte_eth_rx_queue_setup(
pi_nPort,
nQueue,
nRxRingSize,
socket,
performanceMode?NULL:&rx_conf,
pool);
[-- Attachment #2: Type: text/html, Size: 4120 bytes --]
reply other threads:[~2024-08-15 9:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AM9PR09MB4995C20A2CDC990F344079B1A1802@AM9PR09MB4995.eurprd09.prod.outlook.com \
--to=yaroni@radcom.com \
--cc=dev@dpdk.org \
--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).