DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: simonxiaolinux@hotmail.com, alexmay@microsoft.com, kys@microsoft.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 1/7] ether: add function to query for link state interrupt
Date: Wed, 25 Mar 2015 11:11:19 -0700	[thread overview]
Message-ID: <1427307085-5493-2-git-send-email-shemming@brocade.com> (raw)
In-Reply-To: <1427307085-5493-1-git-send-email-shemming@brocade.com>

From: Stephen Hemminger <stephen@networkplumber.org>

Allow application to query whether link state will work.
This is also part of abstracting dependency on PCI.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 lib/librte_ether/rte_ethdev.c | 14 ++++++++++++++
 lib/librte_ether/rte_ethdev.h | 12 ++++++++++++
 2 files changed, 26 insertions(+)

diff --git a/lib/librte_ether/rte_ethdev.c b/lib/librte_ether/rte_ethdev.c
index 03fce08..afe6923 100644
--- a/lib/librte_ether/rte_ethdev.c
+++ b/lib/librte_ether/rte_ethdev.c
@@ -1376,6 +1376,20 @@ rte_eth_dev_start(uint8_t port_id)
 	return 0;
 }
 
+int
+rte_eth_has_link_state(uint8_t port_id)
+{
+	struct rte_eth_dev *dev;
+
+	if (port_id >= nb_ports) {
+		PMD_DEBUG_TRACE("Invalid port_id=%d\n", port_id);
+		return 0;
+	}
+	dev = &rte_eth_devices[port_id];
+
+	return (dev->pci_dev->driver->drv_flags & RTE_PCI_DRV_INTR_LSC) != 0;
+}
+
 void
 rte_eth_dev_stop(uint8_t port_id)
 {
diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h
index 21aa359..124117a 100644
--- a/lib/librte_ether/rte_ethdev.h
+++ b/lib/librte_ether/rte_ethdev.h
@@ -2037,6 +2037,18 @@ extern void rte_eth_link_get_nowait(uint8_t port_id,
 				struct rte_eth_link *link);
 
 /**
+ * Test whether device supports link state interrupt mode.
+ *
+ * @param port_id
+ *   The port identifier of the Ethernet device.
+ * @return
+ *   - (1) if link state interrupt is supported
+ *   - (0) if link state interrupt is not supported
+ */
+extern int
+rte_eth_has_link_state(uint8_t port_id);
+
+/**
  * Retrieve the general I/O statistics of an Ethernet device.
  *
  * @param port_id
-- 
2.1.4

  reply	other threads:[~2015-03-25 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 18:11 [dpdk-dev] [PATCH v2 0/7] Hyperv PMD patches Stephen Hemminger
2015-03-25 18:11 ` Stephen Hemminger [this message]
2015-03-25 18:11 ` [dpdk-dev] [PATCH v2 2/7] pmd: change drivers initialization for pci Stephen Hemminger
2015-03-25 18:11 ` [dpdk-dev] [PATCH v2 3/7] hv: add basic vmbus support Stephen Hemminger
2015-03-25 18:11 ` [dpdk-dev] [PATCH v2 4/7] hv: uio driver Stephen Hemminger
2015-03-25 18:11 ` [dpdk-dev] [PATCH v2 5/7] hv: poll mode driver Stephen Hemminger
2015-03-25 18:11 ` [dpdk-dev] [PATCH v2 6/7] hv: enable driver in common config Stephen Hemminger
2015-03-25 18:11 ` [dpdk-dev] [PATCH v2 7/7] hv: add kernel patch Stephen Hemminger
2015-03-25 19:34   ` KY Srinivasan

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=1427307085-5493-2-git-send-email-shemming@brocade.com \
    --to=stephen@networkplumber.org \
    --cc=alexmay@microsoft.com \
    --cc=dev@dpdk.org \
    --cc=kys@microsoft.com \
    --cc=simonxiaolinux@hotmail.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).