DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vipin Varghese <vipin.varghese@intel.com>
To: dev@dpdk.org, qi.z.zhang@intel.com, marko.kovacevic@intel.com
Cc: deepak.k.jain@intel.com, Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH v1] doc/eth: update document for functional limitation
Date: Wed, 23 May 2018 15:35:59 +0530	[thread overview]
Message-ID: <1527069959-37765-1-git-send-email-vipin.varghese@intel.com> (raw)

ETH APIs dev_attach and dev_dettach can be exercised from primary
process only. Secondary process only maps the resource and does
not have access to internal device list. Hence updating documentation
to reflect the same.

Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
---
 lib/librte_ethdev/rte_ethdev.h | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/lib/librte_ethdev/rte_ethdev.h b/lib/librte_ethdev/rte_ethdev.h
index 36e3984..6afcf9f 100644
--- a/lib/librte_ethdev/rte_ethdev.h
+++ b/lib/librte_ethdev/rte_ethdev.h
@@ -1479,6 +1479,9 @@ int rte_eth_dev_attach(const char *devargs, uint16_t *port_id);
  * This function must be called when the device is in the
  * closed state.
  *
+ * Note:
+ * - Currently supported for primary process only.
+ *
  * @param port_id
  *   The port identifier of the device to detach.
  * @param devname
@@ -1493,6 +1496,9 @@ int rte_eth_dev_detach(uint16_t port_id, char *devname);
  * Convert a numerical speed in Mbps to a bitmap flag that can be used in
  * the bitmap link_speeds of the struct rte_eth_conf
  *
+ * Note:
+ * - Currently supported for primary process only.
+ *
  * @param speed
  *   Numerical speed value in Mbps
  * @param duplex
-- 
2.7.4

             reply	other threads:[~2018-05-23 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23 10:05 Vipin Varghese [this message]
2018-05-24 17:06 ` Thomas Monjalon
2018-05-25  0:44   ` Zhang, Qi Z
2018-05-25  8:34     ` Ferruh Yigit
2018-05-25  9:08       ` Zhang, Qi Z
2018-05-25  9:12         ` Ferruh Yigit

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=1527069959-37765-1-git-send-email-vipin.varghese@intel.com \
    --to=vipin.varghese@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=marko.kovacevic@intel.com \
    --cc=qi.z.zhang@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).