From: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
To: dev@dpdk.org, Yuanhan Liu <yuanhan.liu@linux.intel.com>,
huawei.xie@intel.com
Subject: [dpdk-dev] virtio "how to restart applications" - //dpdk.org/doc/virtio-net-pmd
Date: Thu, 16 Mar 2017 12:39:16 -0700 [thread overview]
Message-ID: <CABK1yFCi1s1syB5JG=U_q7LKW=5tXEdgAczVjgH2npgEARRYDQ@mail.gmail.com> (raw)
So the doc says we should call rte_eth_dev_close() *before* going down. And
I know that especially in dpdk-virtionet in the guest + ovs-dpdk in the
host, the ovs ends up getting stalled/stuck (!!) if I dont close the port
before starting() it when the guest dpdk process comes back up.
Considering that this not done properly can screw up the HOST ovs, and I
want to do everything possible to avoid that, I want to be 200% sure that I
call close even if my process gets a kill -9 .. So obviously the only way
of doing that is to close the port when the dpdk process comes back up and
*before* we init the port. rte_eth_dev_close() is not capable of doing that
as it expects the port parameters to be initialized etc.. before it can be
called. Any other suggestions on what can be done to close on restart
rather than close on going down ? Thought of bouncing this by the alias
before I add a version of close myself that can do this close-on-restart
Rgds,
Gopa.
next reply other threads:[~2017-03-16 19:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 19:39 Gopakumar Choorakkot Edakkunni [this message]
2017-03-17 2:06 ` Yuanhan Liu
2017-03-17 2:48 ` Gopakumar Choorakkot Edakkunni
2017-03-17 4:35 ` Yuanhan Liu
2017-03-17 4:56 ` Gopakumar Choorakkot Edakkunni
2017-03-17 5:13 ` Yuanhan Liu
2017-03-17 5:20 ` Gopakumar Choorakkot Edakkunni
2017-03-17 5:24 ` Yuanhan Liu
2017-03-17 5:30 ` Gopakumar Choorakkot Edakkunni
2017-03-17 5:40 ` Yuanhan Liu
2017-03-17 5:50 ` Gopakumar Choorakkot Edakkunni
2017-03-18 21:32 ` Gopakumar Choorakkot Edakkunni
2017-03-18 21:37 ` Gopakumar Choorakkot Edakkunni
2017-03-18 23:43 ` Gopakumar Choorakkot Edakkunni
2017-03-22 5:32 ` Gopakumar Choorakkot Edakkunni
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='CABK1yFCi1s1syB5JG=U_q7LKW=5tXEdgAczVjgH2npgEARRYDQ@mail.gmail.com' \
--to=gopakumar.c.e@gmail.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=yuanhan.liu@linux.intel.com \
/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).