From: <skoteshwar@marvell.com>
To: Harman Kalra <hkalra@marvell.com>, Jianfeng Tan <jianfeng.tan@intel.com>
Cc: <dev@dpdk.org>, Satha Rao <skoteshwar@marvell.com>, <stable@dpdk.org>
Subject: [PATCH 1/5] interrupts: fix number of bytes read for vdev
Date: Mon, 7 Oct 2024 20:33:59 +0530 [thread overview]
Message-ID: <20241007150403.1680983-1-skoteshwar@marvell.com> (raw)
From: Satha Rao <skoteshwar@marvell.com>
Correct the number of bytes to read during vdev interrupt processing.
The driver sets this value, and the rxtx interrupt handling already
performs this correctly.
Fixes: 99998feec90 ("eal/linux: add interrupt type for vdev")
Cc: stable@dpdk.org
Signed-off-by: Satha Rao <skoteshwar@marvell.com>
---
lib/eal/linux/eal_interrupts.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lib/eal/linux/eal_interrupts.c b/lib/eal/linux/eal_interrupts.c
index 6436f796eb..80eef7ec4b 100644
--- a/lib/eal/linux/eal_interrupts.c
+++ b/lib/eal/linux/eal_interrupts.c
@@ -949,6 +949,10 @@ eal_intr_process_interrupts(struct epoll_event *events, int nfds)
break;
#endif
case RTE_INTR_HANDLE_VDEV:
+ /* For vdev, number of bytes to read is set by driver */
+ bytes_read = rte_intr_efd_counter_size_get(src->intr_handle);
+ call = true;
+ break;
case RTE_INTR_HANDLE_EXT:
bytes_read = 0;
call = true;
--
2.25.1
reply other threads:[~2024-10-07 15:04 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=20241007150403.1680983-1-skoteshwar@marvell.com \
--to=skoteshwar@marvell.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jianfeng.tan@intel.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).