DPDK usage discussions
 help / color / mirror / Atom feed
From: Bing Zhao <bingz@nvidia.com>
To: Igor de Paula <igordptx@gmail.com>, "users@dpdk.org" <users@dpdk.org>
Subject: RE: Upgrade DPDK
Date: Mon, 21 Aug 2023 15:58:26 +0000	[thread overview]
Message-ID: <DM4PR12MB5184D08E5421706E56416EC0D01EA@DM4PR12MB5184.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CALDr01QayQdkpNnp4vRhPZ768GVSzsEuoCtXR-DnF-WDw25mGg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

http://doc.dpdk.org/guides/rel_notes/release_21_11.html

See sections 6.2/6.3/6.4

For examples:
·         ethdev: All enums and macros updated to have RTE_ETH prefix and structures updated to have rte_eth prefix. DPDK components updated to use new names.
Regarding the second question.
Please check the commit “ethdev: fix max Rx packet length” for more details.

BR. Bing

From: Igor de Paula <igordptx@gmail.com>
Sent: Monday, August 21, 2023 6:24 PM
To: users@dpdk.org
Subject: Upgrade DPDK

External email: Use caution opening links or attachments

Hi,
I was running DPDK version 21.08 and I want to upgrade to 22.11 LTS.
I have two issues that I don't find the documentation of. Both are related to Jumbo frames.
It seems the MACRO DEV_RX_OFFLOAD_JUMBO_FRAME
has been removed from rte_ethdev.h. I know the names have changed to RTE_ETH instead of DEV.
Also, the max_rx_pkt_len has been removed from struct rte_rxmode. This makes sense as there is a comment that it should only be used when the jumbo frame is enabled.

The issue is that going through the release notes I have not found anything about depreciation of the MACRO or anything. I looked at the release notes of:
21.11 22.03 22.07 22.11

Can anyone help with this?

Igor

[-- Attachment #2: Type: text/html, Size: 7804 bytes --]

  reply	other threads:[~2023-08-21 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 10:23 Igor de Paula
2023-08-21 15:58 ` Bing Zhao [this message]
2023-08-21 16:14   ` Igor de Paula

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=DM4PR12MB5184D08E5421706E56416EC0D01EA@DM4PR12MB5184.namprd12.prod.outlook.com \
    --to=bingz@nvidia.com \
    --cc=igordptx@gmail.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).