DPDK patches and discussions
 help / color / mirror / Atom feed
From: Mike Bly <bly454@gmail.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, jgrajcia@cisco.com
Subject: Subject: [PATCH] net/memif: Fix memif-tx buffer flags handling
Date: Mon, 6 Jan 2025 11:46:26 -0800	[thread overview]
Message-ID: <CAB3eHOxh3e8wWsjig+puziUnp39tL+J8q6jFS9gsFi3S6vWeag@mail.gmail.com> (raw)

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

Added missing initialization of memif flags field per memif buffer
Bugzilla ID: 1609
Fixes: 09c7e63a71f9 ("net/memif: introduce memory interface PMD")
Cc: stable@dpdk.org
Cc: Jakub Grajciar <jgrajcia@cisco.com>

Signed-off-by: Mike Bly <bly454@gmail.com>
---
 drivers/net/memif/rte_eth_memif.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/net/memif/rte_eth_memif.c
b/drivers/net/memif/rte_eth_memif.c
index bef1606550..63bb72428d 100644
--- a/drivers/net/memif/rte_eth_memif.c
+++ b/drivers/net/memif/rte_eth_memif.c
@@ -712,6 +712,7 @@ eth_memif_tx(void *queue, struct rte_mbuf **bufs,
uint16_t nb_pkts)
 next_in_chain1:
                        d0 = &ring->desc[slot & mask];
                        cp_len = rte_pktmbuf_data_len(mbuf);
+                       d0->flags = 0;

                        rte_memcpy((uint8_t
*)memif_get_buffer(proc_private, d0),
                                rte_pktmbuf_mtod(mbuf, void *), cp_len);
@@ -747,6 +748,7 @@ eth_memif_tx(void *queue, struct rte_mbuf **bufs,
uint16_t nb_pkts)
                        dst_off = 0;
                        dst_len = (type == MEMIF_RING_C2S) ?
                                pmd->run.pkt_buffer_size : d0->length;
+                       d0->flags = 0;

 next_in_chain2:
                        src_off = 0;
-- 
2.43.5

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

                 reply	other threads:[~2025-01-07 10:00 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=CAB3eHOxh3e8wWsjig+puziUnp39tL+J8q6jFS9gsFi3S6vWeag@mail.gmail.com \
    --to=bly454@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jgrajcia@cisco.com \
    --cc=stable@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).