From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Radu Nicolau <radu.nicolau@intel.com>, dev@dpdk.org
Cc: mtetsuyah@gmail.com, declan.doherty@intel.com
Subject: Re: [dpdk-dev] [PATCH] net/null: add set MAC address dev op
Date: Wed, 31 Jan 2018 19:18:42 +0000 [thread overview]
Message-ID: <e966a565-04b5-7fd7-27a0-3b741a56d29f@intel.com> (raw)
In-Reply-To: <1517235632-24080-1-git-send-email-radu.nicolau@intel.com>
On 1/29/2018 2:20 PM, Radu Nicolau wrote:
> Needed if used with net/bonding
>
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> ---
> drivers/net/null/rte_eth_null.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/net/null/rte_eth_null.c b/drivers/net/null/rte_eth_null.c
> index 7cd5c71..511e2b7 100644
> --- a/drivers/net/null/rte_eth_null.c
> +++ b/drivers/net/null/rte_eth_null.c
> @@ -456,6 +456,12 @@ eth_rss_hash_conf_get(struct rte_eth_dev *dev,
> return 0;
> }
>
> +static void
> +eth_mac_address_set(struct rte_eth_dev *dev, struct ether_addr *addr)
> +{
> + memcpy(dev->data->mac_addrs, addr, sizeof(struct ether_addr));
This copy already done in ethdev layer, an empty function will do the work.
> +}
> +
> static const struct eth_dev_ops ops = {
> .dev_start = eth_dev_start,
> .dev_stop = eth_dev_stop,
> @@ -466,6 +472,7 @@ static const struct eth_dev_ops ops = {
> .rx_queue_release = eth_queue_release,
> .tx_queue_release = eth_queue_release,
> .link_update = eth_link_update,
> + .mac_addr_set = eth_mac_address_set,
> .stats_get = eth_stats_get,
> .stats_reset = eth_stats_reset,
> .reta_update = eth_rss_reta_update,
>
next prev parent reply other threads:[~2018-01-31 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 14:20 Radu Nicolau
2018-01-31 19:18 ` Ferruh Yigit [this message]
2018-02-01 10:42 ` [dpdk-dev] [PATCH 1/3] " Radu Nicolau
2018-02-01 10:45 ` Radu Nicolau
2018-02-01 10:47 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2018-02-05 14:40 ` Ferruh Yigit
2018-02-05 14:46 ` 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=e966a565-04b5-7fd7-27a0-3b741a56d29f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=mtetsuyah@gmail.com \
--cc=radu.nicolau@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).