From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 194] vhost pmd has become unusable from secondary processes.
Date: Mon, 21 Jan 2019 05:45:06 +0000 [thread overview]
Message-ID: <bug-194-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=194
Bug ID: 194
Summary: vhost pmd has become unusable from secondary
processes.
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: CONFIRMED
Severity: critical
Priority: Normal
Component: vhost/virtio
Assignee: dev@dpdk.org
Reporter: oda@valinux.co.jp
Target Milestone: ---
This problem was discovered when trying to migrate the base of
SPP(http://git.dpdk.org/apps/spp/) from DPDK v18.08 to v18.11.
In SPP, secondary processes attach (rte_eal_hotplug_add) and use vhost pmd (ex.
devargs: "eth_vhost0,iface=/tmp/sock0,queues=1,client=1").
It was no problem under DPDK v18.08 but secondary processes crash under v18.11.
As a result of some investigations, it was found that the direct cause of crash
is because no value is set (i.e. null pointer) for [rt]x_pkt_burst member of
rte_eth_dev of vhost.
Certainly there is no place to set on the code.
(Is this comment related to something?
https://github.com/DPDK/dpdk/blob/master/drivers/net/vhost/rte_eth_vhost.c#L1352
)
In addition, even if the value is set, it will not work.
This is because eth_vhost_[rt]x refers to vid which is the index of
vhsot_devices
(https://github.com/DPDK/dpdk/blob/master/lib/librte_vhost/vhost.c#L28).
vhost_devices is per process data (i.e. not shared data) and the primary
process only uses vhost_devices under v18.11 (unlike v18.08) and it is not
accessed from
secondary processes.
Perhaps some fix, such as making vhost_devices a shared data, is necessary.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-01-21 5:45 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=bug-194-3@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.