From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] e1000: enable allmulticast support for VF
Date: Mon, 15 Jun 2015 17:09:14 +0200 [thread overview]
Message-ID: <4826575.vIM4VYrcXt@xps13> (raw)
In-Reply-To: <1432824407-11415-1-git-send-email-yury.kylulin@intel.com>
We still have no maintainer for e1000.
Anyone to double-check this short patch?
2015-05-28 17:46, Yury Kylulin:
> Add support to enable and disable reception of all multicast packets by the VF using standard API
> rte_eth_allmulticast_enable()/rte_eth_allmulticast_disable().
>
> Signed-off-by: Yury Kylulin <yury.kylulin@intel.com>
[...]
> +static void
> +igbvf_allmulticast_enable(struct rte_eth_dev *dev)
> +{
> + struct e1000_hw *hw = E1000_DEV_PRIVATE_TO_HW(dev->data->dev_private);
> +
> + e1000_promisc_set_vf(hw, e1000_promisc_multicast);
> +}
> +
> +static void
> +igbvf_allmulticast_disable(struct rte_eth_dev *dev)
> +{
> + struct e1000_hw *hw = E1000_DEV_PRIVATE_TO_HW(dev->data->dev_private);
> +
> + e1000_promisc_set_vf(hw, e1000_promisc_disabled);
> +}
The values come from this enum:
enum e1000_promisc_type {
e1000_promisc_disabled = 0, /* all promisc modes disabled */
e1000_promisc_unicast = 1, /* unicast promiscuous enabled */
e1000_promisc_multicast = 2, /* multicast promiscuous enabled */
e1000_promisc_enabled = 3, /* both uni and multicast promisc */
next prev parent reply other threads:[~2015-06-15 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 14:46 Yury Kylulin
2015-06-15 15:09 ` Thomas Monjalon [this message]
2015-06-16 1:36 ` Lu, Wenzhuo
2015-07-14 0:59 ` Lu, Wenzhuo
2016-02-09 9:09 ` [dpdk-dev] [PATCH v2] e1000: enable promiscuous and " Yury Kylulin
2016-02-15 1:14 ` Lu, Wenzhuo
2016-02-15 10:44 ` Kylulin, Yury
2016-02-16 0:43 ` Lu, Wenzhuo
2016-02-26 17:28 ` 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=4826575.vIM4VYrcXt@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
/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).