From: Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>
To: Jerin Jacob <jerinjacobk@gmail.com>, <thomas@monjalon.net>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [PATCH] examples/l3fwd: fix issue with MTU set on event mode
Date: Mon, 18 Jul 2022 20:00:02 +0530 [thread overview]
Message-ID: <95117186-c447-494c-8cd8-3591bf2da4af@marvell.com> (raw)
In-Reply-To: <CALBAE1PYwDLuLkDwh0HKN0oR_R2+MwvkubOgL_11poS4GTYCwg@mail.gmail.com>
Ping.
On 2022-06-02 1:15 PM, Jerin Jacob wrote:
> On Thu, Apr 21, 2022 at 7:47 PM Nithin Dabilpuram
> <ndabilpuram@marvell.com> wrote:
>>
>> MTU configuration is missing for ethdev when using eventmode
>> when user provides it via "--max-pkt-len" config. It is only
>> done in poll mode setup. Fix the event mode setup code to
>> do the same.
>>
>> Fixes: 1bb4a528c41f ("ethdev: fix max Rx packet length")
>> Cc: ferruh.yigit@intel.com
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
>
>
>> ---
>> examples/l3fwd/l3fwd.h | 5 +++++
>> examples/l3fwd/l3fwd_event.c | 6 ++++++
>> examples/l3fwd/main.c | 4 ++--
>> 3 files changed, 13 insertions(+), 2 deletions(-)
>>
>> diff --git a/examples/l3fwd/l3fwd.h b/examples/l3fwd/l3fwd.h
>> index ad39496..b0bfdcc 100644
>> --- a/examples/l3fwd/l3fwd.h
>> +++ b/examples/l3fwd/l3fwd.h
>> @@ -107,6 +107,8 @@ extern struct lcore_conf lcore_conf[RTE_MAX_LCORE];
>>
>> extern struct parm_cfg parm_config;
>>
>> +extern uint32_t max_pkt_len;
>> +
>> /* Send burst of packets on an output interface */
>> static inline int
>> send_burst(struct lcore_conf *qconf, uint16_t n, uint16_t port)
>> @@ -193,6 +195,9 @@ is_valid_ipv4_pkt(struct rte_ipv4_hdr *pkt, uint32_t link_len)
>> int
>> init_mem(uint16_t portid, unsigned int nb_mbuf);
>>
>> +int config_port_max_pkt_len(struct rte_eth_conf *conf,
>> + struct rte_eth_dev_info *dev_info);
>> +
>> /* Function pointers for LPM, EM or FIB functionality. */
>> void
>> setup_lpm(const int socketid);
>> diff --git a/examples/l3fwd/l3fwd_event.c b/examples/l3fwd/l3fwd_event.c
>> index 7a40129..e72add8 100644
>> --- a/examples/l3fwd/l3fwd_event.c
>> +++ b/examples/l3fwd/l3fwd_event.c
>> @@ -73,6 +73,12 @@ l3fwd_eth_dev_port_setup(struct rte_eth_conf *port_conf)
>> rte_panic("Error during getting device (port %u) info:"
>> "%s\n", port_id, strerror(-ret));
>>
>> + ret = config_port_max_pkt_len(&local_port_conf, &dev_info);
>> + if (ret != 0)
>> + rte_exit(EXIT_FAILURE,
>> + "Invalid max packet length: %u (port %u)\n",
>> + max_pkt_len, port_id);
>> +
>> if (dev_info.tx_offload_capa & RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE)
>> local_port_conf.txmode.offloads |=
>> RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE;
>> diff --git a/examples/l3fwd/main.c b/examples/l3fwd/main.c
>> index a629198..6585c8b 100644
>> --- a/examples/l3fwd/main.c
>> +++ b/examples/l3fwd/main.c
>> @@ -135,7 +135,7 @@ static struct rte_eth_conf port_conf = {
>> },
>> };
>>
>> -static uint32_t max_pkt_len;
>> +uint32_t max_pkt_len;
>>
>> static struct rte_mempool *pktmbuf_pool[RTE_MAX_ETHPORTS][NB_SOCKETS];
>> static struct rte_mempool *vector_pool[RTE_MAX_ETHPORTS];
>> @@ -1136,7 +1136,7 @@ eth_dev_get_overhead_len(uint32_t max_rx_pktlen, uint16_t max_mtu)
>> return overhead_len;
>> }
>>
>> -static int
>> +int
>> config_port_max_pkt_len(struct rte_eth_conf *conf,
>> struct rte_eth_dev_info *dev_info)
>> {
>> --
>> 2.8.4
>>
next prev parent reply other threads:[~2022-07-18 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 14:16 Nithin Dabilpuram
2022-06-02 7:45 ` Jerin Jacob
2022-07-18 14:30 ` Nithin Kumar Dabilpuram [this message]
2022-10-10 21:55 ` Thomas Monjalon
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=95117186-c447-494c-8cd8-3591bf2da4af@marvell.com \
--to=ndabilpuram@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).