From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "David Harton (dharton)" <dharton@cisco.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] How To Handle Hot Remove?
Date: Fri, 29 Apr 2016 08:53:45 +0200 [thread overview]
Message-ID: <2894388.k7NLsDXYx5@xps13> (raw)
In-Reply-To: <c4831a0f3c574ca7bffd463b8a2301a7@XCH-RCD-016.cisco.com>
2016-04-28 23:50, David Harton:
> 1) What notification does DPDK provide the application or to gracefully stop the device?
A rework of hotplug is in progress:
http://dpdk.org/ml/archives/dev/2016-April/037686.html
Notifications needs to be added.
> 2) Is there any kind of ordering the application has to follow before calling rte_eth_dev_detatch()?
The order is "stop - close - detach":
/**
* Detach a Ethernet device specified by port identifier.
* This function must be called when the device is in the
* closed state.
prev parent reply other threads:[~2016-04-29 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 23:50 David Harton (dharton)
2016-04-29 6:53 ` Thomas Monjalon [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=2894388.k7NLsDXYx5@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dharton@cisco.com \
--cc=users@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).