From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: La Rus <zator@yandex.ru>
Cc: users@dpdk.org
Subject: Re: Added x710 --- got errno:22 from rte_eth_dev_configure()
Date: Thu, 30 Mar 2023 15:54:14 +0300 [thread overview]
Message-ID: <20230330155414.2b5d1d26@sovereign> (raw)
In-Reply-To: <e1da40de-e842-a623-44c6-8b3907df0bcb@yandex.ru>
Hi,
2023-03-30 15:01 (UTC+0300), La Rus:
> 30-03-2023 14:49:54.701 145081 [CGWPROC\tootoo2_cgw_start:1378]
> : *l_dev_info.tx_offload_capa = 0x00119fbf*
> 30-03-2023 14:49:54.701 145081 [CGWPROC\tootoo2_cgw_start:1379]
> : *l_port_conf.txmode.offloads = 0x00010000*
> 30-03-2023 14:49:54.701 145081 [CGWPROC\tootoo2_cgw_start:1380]
> : l_dev_info.rx_offload_capa = 0x0009266f
> 30-03-2023 14:49:54.701 145081 [CGWPROC\tootoo2_cgw_start:1381]
> : l_port_conf.rxmode.offloads = 0x00000000
> 30-03-2023 14:49:54.701 145081 [CGWPROC\tootoo2_cgw_start:1384]
> : l_dev_info.max_tx_queues = 320
> 30-03-2023 14:49:54.701 145081 [CGWPROC\tootoo2_cgw_start:1386]
> : l_nb_tx_queues = 8
> 30-03-2023 14:49:54.701 145081 [CGWPROC\tootoo2_cgw_start:1388]
> : l_dev_info.max_rx_queues = 320
> 30-03-2023 14:49:54.701 145081 [CGWPROC\tootoo2_cgw_start:1390]
> : l_nb_rx_queues = 8
> *Ethdev port_id=0 requested Tx offloads 0x10000 doesn't match Tx
> offloads capabilities 0x2a03f in rte_eth_dev_configure()*
> 30-03-2023 14:49:54.701 145081 [CGWPROC\tootoo2_cgw_start:1396]
> %TTR2CGW-F: _PEA00:, rte_eth_dev_configure()->-22
>
> *PEA00 == Device:0000:01:00.0*
>
>
> Is there what I'm need to check ?
The message says it all:
you're requesting Tx offloads not supported by the HW.
0x10000 == RTE_BIT(16) == RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE,
which is supported by i40e but not ixgbe PMD.
Can it be that you use rte_eth_dev_info.tx_offload_capa from i40e port
to fill txmode.offloads for ixgbe port by mistake?
next prev parent reply other threads:[~2023-03-30 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 12:01 La Rus
2023-03-30 12:54 ` Dmitry Kozlyuk [this message]
2023-03-30 13:42 ` Ruslan R. Laishev
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=20230330155414.2b5d1d26@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=users@dpdk.org \
--cc=zator@yandex.ru \
/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).