From: Yong Wang <yongwang@vmware.com>
To: Remy Horton <remy.horton@intel.com>,
"helin.zhang@intel.com" <helin.zhang@intel.com>,
"huawei.xie@intel.com" <huawei.xie@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1 3/3] drivers/net/vmxnet3: Add ethdev functions
Date: Tue, 16 Feb 2016 23:42:09 +0000 [thread overview]
Message-ID: <7B3631D5-39A4-4DD2-8E11-9B62CE9B608B@vmware.com> (raw)
In-Reply-To: <1453970895-2639-4-git-send-email-remy.horton@intel.com>
On 1/28/16, 12:48 AM, "Remy Horton" <remy.horton@intel.com> wrote:
>Implements driver support for fetching Tx and Rx queue information, and
>setting of MAC address.
>
>Signed-off-by: Remy Horton <remy.horton@intel.com>
>---
> doc/guides/rel_notes/release_2_3.rst | 5 +++
> drivers/net/vmxnet3/vmxnet3_ethdev.c | 60 ++++++++++++++++++++++++++++++++++++
> 2 files changed, 65 insertions(+)
>
>diff --git a/doc/guides/rel_notes/release_2_3.rst b/doc/guides/rel_notes/release_2_3.rst
>index e6dab98..6a50e26 100644
>--- a/doc/guides/rel_notes/release_2_3.rst
>+++ b/doc/guides/rel_notes/release_2_3.rst
>@@ -13,6 +13,11 @@ New Features
>
> Implemented Tx & Rx queue information fetching functions.
>
>+* **vmxnet3: Added ethdev support functions.**
>+
>+ Implemented Tx & Rx queue information fetching and MAC address setting
>+ functions.
>+
>
> Resolved Issues
> ---------------
>diff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.c b/drivers/net/vmxnet3/vmxnet3_ethdev.c
>index c363bf6..f7000d6 100644
>--- a/drivers/net/vmxnet3/vmxnet3_ethdev.c
>+++ b/drivers/net/vmxnet3/vmxnet3_ethdev.c
>@@ -91,6 +91,15 @@ static int vmxnet3_dev_vlan_filter_set(struct rte_eth_dev *dev,
> static void vmxnet3_dev_vlan_offload_set(struct rte_eth_dev *dev, int mask);
> static void vmxnet3_dev_vlan_offload_set_clear(struct rte_eth_dev *dev,
> int mask, int clear);
>+static void vmxnet3_mac_addr_set(struct rte_eth_dev *dev,
>+ struct ether_addr *mac_addr);
>+static void vmxnet3_rxq_info_get(struct rte_eth_dev *dev,
>+ uint16_t queue_id,
>+ struct rte_eth_rxq_info *qinfo);
>+static void vmxnet3_txq_info_get(struct rte_eth_dev *dev,
>+ uint16_t queue_id,
>+ struct rte_eth_txq_info *qinfo);
>+
>
> #if PROCESS_SYS_EVENTS == 1
> static void vmxnet3_process_events(struct vmxnet3_hw *);
>@@ -124,6 +133,9 @@ static const struct eth_dev_ops vmxnet3_eth_dev_ops = {
> .rx_queue_release = vmxnet3_dev_rx_queue_release,
> .tx_queue_setup = vmxnet3_dev_tx_queue_setup,
> .tx_queue_release = vmxnet3_dev_tx_queue_release,
>+ .mac_addr_set = vmxnet3_mac_addr_set,
>+ .rxq_info_get = vmxnet3_rxq_info_get,
>+ .txq_info_get = vmxnet3_txq_info_get,
> };
>
> static const struct rte_memzone *
>@@ -922,6 +934,54 @@ vmxnet3_process_events(struct vmxnet3_hw *hw)
> }
> #endif
>
>+static void vmxnet3_mac_addr_set(struct rte_eth_dev *dev,
>+ struct ether_addr *mac_addr)
>+{
>+ struct vmxnet3_hw *hw = dev->data->dev_private;
>+ uint32_t mac_hi, mac_lo;
>+
>+ memcpy(&mac_lo, mac_addr, 4);
>+ memcpy(&mac_hi, mac_addr + 4, 2);
>+ VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_MACL, mac_lo);
>+ VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_MACH, mac_hi);
>+
>+ ether_addr_copy(mac_addr, &dev->data->mac_addrs[0]);
Is this needed? Looks like rte_eth_dev_default_mac_addr_set() already
called it before calling the callback. Or is there another path that
this is not done?
>+}
>+
>+static void vmxnet3_rxq_info_get(struct rte_eth_dev *dev,
>+ uint16_t queue_id,
>+ struct rte_eth_rxq_info *qinfo)
>+{
>+ struct vmxnet3_rx_queue *rxq;
>+
>+ rxq = dev->data->rx_queues[queue_id];
>+
>+ qinfo->mp = rxq->mp;
>+ qinfo->scattered_rx = dev->data->scattered_rx;
>+ qinfo->nb_desc = dev->data->nb_rx_queues;
nb_rx_queues should be rxq->cmd_ring[0].size.
Furthermore, each rx queue have two rings that could in theory
be of different size. But since this info only, I think it’s
good enough to just report ring0’s size here.
>+
>+ /* Driver does not use these values */
>+ qinfo->conf.rx_free_thresh = 0;
>+ qinfo->conf.rx_drop_en = 0;
>+ qinfo->conf.rx_deferred_start = 0;
What about rx_thresh here?
>+}
>+
>+static void vmxnet3_txq_info_get(struct rte_eth_dev *dev,
>+ __rte_unused uint16_t queue_id,
>+ struct rte_eth_txq_info *qinfo)
>+{
>+ qinfo->nb_desc = dev->data->nb_tx_queues;
nb_tx_queues here should be txq->cmd_ring.size
>+
>+ /* Driver does not use these values */
>+ qinfo->conf.tx_thresh.pthresh = 0;
>+ qinfo->conf.tx_thresh.hthresh = 0;
>+ qinfo->conf.tx_thresh.wthresh = 0;
>+ qinfo->conf.tx_free_thresh = 0;
>+ qinfo->conf.tx_rs_thresh = 0;
>+ qinfo->conf.txq_flags = 0;
>+ qinfo->conf.tx_deferred_start = 0;
>+}
>+
> static struct rte_driver rte_vmxnet3_driver = {
> .type = PMD_PDEV,
> .init = rte_vmxnet3_pmd_init,
>--
>2.5.0
>
next prev parent reply other threads:[~2016-02-16 23:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 8:48 [dpdk-dev] [PATCH v1 0/3] Add missing ethdev driver support Remy Horton
2016-01-28 8:48 ` [dpdk-dev] [PATCH v1 1/3] drivers/net/i40e: Add ethdev functions Remy Horton
2016-02-23 2:06 ` Zhang, Helin
2016-02-24 10:32 ` Remy Horton
2016-02-24 10:43 ` Ananyev, Konstantin
2016-01-28 8:48 ` [dpdk-dev] [PATCH v1 2/3] drivers/net/virtio: " Remy Horton
2016-01-28 8:48 ` [dpdk-dev] [PATCH v1 3/3] drivers/net/vmxnet3: " Remy Horton
2016-02-16 23:42 ` Yong Wang [this message]
2016-02-16 12:02 ` [dpdk-dev] [PATCH v1 0/3] Add missing ethdev driver support Bruce Richardson
2016-02-16 18:54 ` Stephen Hemminger
2016-02-23 12:19 ` Remy Horton
2016-03-04 15:25 ` [dpdk-dev] [PATCH v2 0/2] " Remy Horton
2016-03-04 15:25 ` [dpdk-dev] [PATCH v2 1/2] drivers/net/i40e: add ethdev functions Remy Horton
2016-03-04 15:25 ` [dpdk-dev] [PATCH v2 2/2] drivers/net/vmxnet3: " Remy Horton
2016-03-04 19:12 ` Yong Wang
2016-03-04 20:34 ` Stephen Hemminger
2016-03-07 12:26 ` Remy Horton
[not found] ` <20160307080747.02cc1f1b@xeon-e3>
2016-03-07 17:06 ` Remy Horton
2016-03-07 19:19 ` Stephen Hemminger
2016-03-09 13:29 ` [dpdk-dev] [PATCH v3 0/1] Add missing ethdev driver support Remy Horton
2016-03-09 13:29 ` [dpdk-dev] [PATCH v3 1/1] drivers/net/i40e: add ethdev functions Remy Horton
2016-03-10 12:25 ` Mcnamara, John
2016-03-14 10:22 ` Bruce Richardson
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=7B3631D5-39A4-4DD2-8E11-9B62CE9B608B@vmware.com \
--to=yongwang@vmware.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=huawei.xie@intel.com \
--cc=remy.horton@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).