From: "Liu, Yong" <yong.liu@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/5]support filter of unicast and multicast MAC address for VF on Fortville
Date: Thu, 25 Sep 2014 08:17:44 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10CE0FA5@SHSMSX103.ccr.corp.intel.com> (raw)
Tested-by: Liu Yong <yong.liu at intel.com>
This patch set has been tested by Intel.
Please see information as the following:
Host:
OS : Fedora 20 x86_64
Kernel : 3.11.10-301
GCC : 4.8.3
CPU : Intel Xeon CPU E5-2680 v2 @ 2.80GHz
NIC : 2*40G (8086:1583)
Qemu : 1.6.2
libvirt : 1.1.3
Guest:
OS : Fedora 20 x86_64
Kernel : 3.11.10-301
GCC : 4.8.3
We verified perfect and hash match filter of unicast and multicast MAC address for VF work normally on FVL.
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jijiang Liu
> Sent: Tuesday, September 23, 2014 11:30 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 0/5]support filter of unicast and multicast MAC
> address for VF on Fortville
>
> The patch set enhances MACVLAN filter configurability and supports perfect
> and hash match filter of unicast
> and multicast MAC address for VF on Fortville.
>
> It mainly includes:
> - Use new filter mechanism discussed at
> http://dpdk.org/ml/archives/dev/2014-September/005179.html.
> - Enhance MACVLAN filter to be configurable. Now the following options are
> configurable:
> 1. Perfect match of MAC address
> 2. Perfect match of MAC address and VLAN ID
> 3. Hash match of MAC address
> 4. Hash match of MAC address and perfect match of VLAN ID
> 5. To Queue: use MAC and VLAN to point to a queue
> - Support perfect and hash match of unicast and multicast MAC address for
> VF for i40e
>
>
> jijiangl (5):
> Use new filter framework
> Add new definations for MACVLAN filter enhancement in rte_eth_ctrl.h file
> Change parameters of MAC/VLAN filter to be configurable
> Add VF MACVLAN filter handle for i40e
> Test VF MACVLAN filter for i40e
>
> app/test-pmd/cmdline.c | 115 +++++++++++++-
> lib/librte_ether/Makefile | 1 +
> lib/librte_ether/rte_eth_ctrl.h | 104 ++++++++++++
> lib/librte_ether/rte_ethdev.c | 33 ++++
> lib/librte_ether/rte_ethdev.h | 48 ++++++-
> lib/librte_pmd_i40e/i40e_ethdev.c | 321
> ++++++++++++++++++++++++++++++++-----
> lib/librte_pmd_i40e/i40e_ethdev.h | 18 ++-
> lib/librte_pmd_i40e/i40e_pf.c | 7 +-
> 8 files changed, 601 insertions(+), 46 deletions(-)
> create mode 100644 lib/librte_ether/rte_eth_ctrl.h
>
> --
> 1.7.7.6
next reply other threads:[~2014-09-25 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 8:17 Liu, Yong [this message]
2014-10-13 2:28 ` Liu, Jijiang
-- strict thread matches above, loose matches on Subject: below --
2014-09-23 3:29 Jijiang Liu
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=86228AFD5BCD8E4EBFD2B90117B5E81E10CE0FA5@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.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).