From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1181] [DPDK-23.03]loopback_virtio_user_server_mode_cbdma: testpmd can't loop packets after start dpdk-pdump app Immediately
Date: Mon, 20 Mar 2023 09:01:21 +0000 [thread overview]
Message-ID: <bug-1181-3-Gvm4vtVtQC@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1181-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1181
lingwei (weix.ling@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from lingwei (weix.ling@intel.com) ---
The patch has been merged, and verified PASSED.
OS: Ubuntu 22.04.1 LTS/Linux 5.15.45-051545-generic
commit f1d0993e034e39968a2c80a8561b46c260c27487 (HEAD -> main, origin/main,
origin/HEAD)
Author: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri Mar 17 09:59:41 2023 -0700
app/testpmd: fix interactive mode on Windows
The cmdline_poll() function is broken and was not fully tested,
go back to using cmdline_interact().
Instead, use sigaction() to cancel read character on Unix OS's
and a new helper to cancel I/O on Windows.
Bugzilla ID: 1180
Fixes: 0fd1386c30c3 ("app/testpmd: cleanup cleanly from signal")
Cc: stable@dpdk.org
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3725 bytes --]
prev parent reply other threads:[~2023-03-20 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 3:48 [Bug 1181] [DPDK-23.03]loopback_virtio_user_server_mode_cbdma: testpmd can't loop packets after start dpdk-pdump app Immediately bugzilla
2023-03-20 9:01 ` bugzilla [this message]
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=bug-1181-3-Gvm4vtVtQC@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.