From: Sriram Yagnaraman <sriram.yagnaraman@ericsson.com>
To: Mike Bly <bly454@gmail.com>, <dev@dpdk.org>
Cc: Sriram Yagnaraman <sriram.yagnaraman@ericsson.com>,
<stable@dpdk.org>, <jgrajcia@cisco.com>
Subject: Re: [PATCH v2] net/memif: Fix memif-rx buffer linking
Date: Mon, 16 Mar 2026 09:49:06 +0100 [thread overview]
Message-ID: <20260316085000.3492548-1-sriram.yagnaraman@ericsson.com> (raw)
In-Reply-To: <CAB3eHOwcEg_7A1rsDFm7QuGQXd72XscEkxg0PcgkUqe8-ZVP-A@mail.gmail.com>
Hi Mike,
Do you know the status of this patch? It looks like it hasn't received any
review since it was posted in January 2025.
We've independently hit the same bug (dst_off reset per-descriptor
instead of per-packet in the RX slow path) and your fix solves our
issue.
If this patch is stale and unlikely to be picked up, I can send a
new patchset against the latest tree that also includes a
boundary check for MEMIF_DESC_FLAG_NEXT when n_slots is
exhausted.
Let me know if you'd prefer to respin your series or if I should send
a new one.
Thanks,
Sriram
next prev parent reply other threads:[~2026-03-16 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 18:22 [PATCH v2] net/memif: Fix memif-rx buffer linking Mike Bly
2025-01-08 15:36 ` Stephen Hemminger
2026-03-16 8:49 ` Sriram Yagnaraman [this message]
2026-03-16 15:13 ` Mike Bly
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=20260316085000.3492548-1-sriram.yagnaraman@ericsson.com \
--to=sriram.yagnaraman@ericsson.com \
--cc=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