DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] expectation from rte_eth_dev_stop(start)
@ 2018-07-08  6:21 Shahaf Shuler
  0 siblings, 0 replies; only message in thread
From: Shahaf Shuler @ 2018-07-08  6:21 UTC (permalink / raw)
  To: arybchenko, ferruh.yigit, Thomas Monjalon; +Cc: dev

Hi ethdev maintainers,

I am looking for the exact expectation from the PMD upon a call for rte_eth_dev_stop.  The doc is a bit lacking[1].

Assuming stop should do the opposite of start[2],
Does it mean after call to dev_stop the DPDK port should no longer receive traffic?
What should be the link status after a call to dev_stop? From [2] it seems like a don't care since the link_status callback is not enabled.

[1]
/**
 * Stop an Ethernet device. The device can be restarted with a call to
* rte_eth_dev_start()
 *
 * @param port_id
 *   The port identifier of the Ethernet device.
 */
void rte_eth_dev_stop(uint16_t port_id);

[2]
/**
 * Start an Ethernet device.
 *
 * The device start step is the last one and consists of setting the configured
* offload features and in starting the transmit and the receive units of the
 * device.
 * On success, all basic functions exported by the Ethernet API (link status,
 * receive/transmit, and so on) can be invoked.
 *
 * @param port_id
 *   The port identifier of the Ethernet device.
 * @return
 *   - 0: Success, Ethernet device started.
 *   - <0: Error code of the driver device start function.
 */
int rte_eth_dev_start(uint16_t port_id);

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2018-07-08  6:21 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-07-08  6:21 [dpdk-dev] expectation from rte_eth_dev_stop(start) Shahaf Shuler

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).