From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v3 2/4] net/netvsc: add hyper-v netvsc network device
Date: Wed, 18 Apr 2018 10:36:42 -0700 [thread overview]
Message-ID: <20180418103642.0d640375@xeon-e3> (raw)
In-Reply-To: <438086f5-76f4-3c72-5c2f-b54577d12af2@intel.com>
On Wed, 18 Apr 2018 14:19:52 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> > +/* enables testpmd to collect per queue stats. */
> > +static int
> > +hn_queue_stats_mapping_set(__rte_unused struct rte_eth_dev *eth_dev,
> > + __rte_unused uint16_t queue_id,
> > + __rte_unused uint8_t stat_idx,
> > + __rte_unused uint8_t is_rx)
> > +{
> > + return 0;
> > +}
>
> IS this dev_ops needed at all?
This is leftover. It is clone of original from virtio.
Not sure why (or if) it is needed. Will drop and see.
next prev parent reply other threads:[~2018-04-18 17:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:53 [dpdk-dev] [PATCH v3 0/4] Hyper-V Netvsc PMD Stephen Hemminger
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 1/4] bus/vmbus: add hyper-v virtual bus support Stephen Hemminger
2018-04-18 13:16 ` Ferruh Yigit
2018-04-18 16:01 ` Stephen Hemminger
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 2/4] net/netvsc: add hyper-v netvsc network device Stephen Hemminger
2018-04-18 13:19 ` Ferruh Yigit
2018-04-18 16:04 ` Stephen Hemminger
2018-04-18 17:36 ` Stephen Hemminger [this message]
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 3/4] net/netvsc: add documentation Stephen Hemminger
2018-04-18 13:25 ` Ferruh Yigit
2018-04-18 16:03 ` Stephen Hemminger
2018-04-18 16:16 ` Ferruh Yigit
2018-04-19 12:37 ` Hemant Agrawal
2018-04-17 21:53 ` [dpdk-dev] [PATCH v3 4/4] bus/vmbus and net/netvsc: add meson build support Stephen Hemminger
2018-04-18 13:25 ` [dpdk-dev] [PATCH v3 0/4] Hyper-V Netvsc PMD 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=20180418103642.0d640375@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=sthemmin@microsoft.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).