test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Xu, HuilongX" <huilongx.xu@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [dts 3/4] [PATCH V1] add generic_filter test plan
Date: Tue, 26 May 2015 05:33:21 +0000	[thread overview]
Message-ID: <DF2A19295B96364286FEB7F3DDA27A4601112DCB@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E10E338EC@SHSMSX103.ccr.corp.intel.com>

Hi yong,
For your comments, I check with as below.

> -----Original Message-----
> From: Liu, Yong
> Sent: Tuesday, May 26, 2015 10:11 AM
> To: Xu, HuilongX; dts@dpdk.org
> Subject: RE: [dts] [dts 3/4] [PATCH V1] add generic_filter test plan
> 
> Huilong, please see my comments below.
> 
> > -----Original Message-----
> > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of huilong,xu
> > Sent: Monday, May 25, 2015 4:54 PM
> > To: dts@dpdk.org
> > Subject: [dts] [dts 3/4] [PATCH V1] add generic_filter test plan
> >
> > From: huilong xu <huilongx.xu@intel.com>
> >
> >
> > Signed-off-by: huilong xu <huilongx.xu@intel.com>
> > ---
> >  test_plans/generic_filter_test_plan.rst |  516
> > +++++++++++++++++++++++++++++++
> >  1 files changed, 516 insertions(+), 0 deletions(-)
> >  create mode 100644 test_plans/generic_filter_test_plan.rst
> >
> > diff --git a/test_plans/generic_filter_test_plan.rst
> > b/test_plans/generic_filter_test_plan.rst
> > new file mode 100644
> > index 0000000..b106180
> > --- /dev/null
> > +++ b/test_plans/generic_filter_test_plan.rst
> > @@ -0,0 +1,516 @@
> > +  .. Copyright (c) <2015>, Intel Corporation
> > +   All rights reserved.
> > +
> > +   Redistribution and use in source and binary forms, with or without
> > +   modification, are permitted provided that the following conditions
> > +   are met:
> > +
> > +   - Redistributions of source code must retain the above copyright
> > +     notice, this list of conditions and the following disclaimer.
> > +
> > +   - Redistributions in binary form must reproduce the above copyright
> > +     notice, this list of conditions and the following disclaimer in
> > +     the documentation and/or other materials provided with the
> > +     distribution.
> > +
> > +   - Neither the name of Intel Corporation nor the names of its
> > +     contributors may be used to endorse or promote products derived
> > +     from this software without specific prior written permission.
> > +
> > +   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> > +   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> > +   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
> > +   FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
> > +   COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
> > +   INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> > +   (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
> > +   SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> > +   HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
> > +   STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> > +   ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
> > +   OF THE POSSIBILITY OF SUCH DAMAGE.
> > +
> > +
> > +Description
> > +=====================================================
> > +This document provides the plan for testing the generic filter feature
> of
> > 10GbE and 1GbE Ethernet Controller.
> 
> This feature should also cover 40GE FVL card.
>
I will update the NIC info as next version patch
 
> In `testpmd`, app provides Generic
> > Filter API to manage filter rules for kinds of packets, and calls the
> API
> > to manage HW filters in HW, or SW filters in SW table.
> > +
> > +* A generic filter provides an ability to identify specific  flows or
> > sets of  flows and routes them to dedicated queues.
> > +* Based on the Generic Filter mechanism, all the SYN packets are placed
> > in an assigned queue.
> > +* Based on the Generic Filter mechanism, all packets belonging to L3/L4
> > flows to be placed in a specific HW queue.Each filter consists of a 5-
> > tuple (protocol, source and destination IP addresses, source and
> > destination TCP/UDP/SCTP port) and routes packets into one of the Rx
> > queues
> > +* L2 Ethertype Filters provides an ability to identify packets by their
> > L2 Ethertype and assigns them to receive queues.
> > +`Testpmd` app is used to test all types of HW filters. Case 1~9 are the
> > function test for the above app while case 11,12 are the performance
> test
> > for Niantic, I350, 82580 and 82576.
> > +
> > +
> > +Prerequisites
> > +===================================================
> > +Assuming that ports ``0`` and ``1`` are connected to a traffic
> > generator's port ``A`` and ``B``.
> > +
> > +Setup for ``testpmd``
> > +-----------------------------------------------------------------
> > +Launch the app ``testpmd`` with the following arguments::
> > +
> > +    ./testpmd -c fffff -n 4 -- -i --disable-rss --rxq=4 --txq=4 --nb-
> > cores=16 --nb-ports=2
> > +
> > +The -n command is used to select the number of memory channels. It
> should
> > be matched with the number of memory channels on that setup. The value
> of
> > rxq and txq is 1 by default, it's necessary  to increase them, and make
> > sure rxq and txq more than one. At the same time rss is enable by
> default,
> > so disable it. Map port queues to statistic counter registers.::
> > +
> > +    testpmd>set stat_qmap rx 0 0 0
> > +    testpmd>set stat_qmap rx 0 1 1
> > +    testpmd>set stat_qmap rx 0 2 2
> > +    testpmd>set stat_qmap rx 0 3 3
> > +Setup for receive all packet and disable vlan strip function::
> > +
> > +    testpmd>vlan set strip off 0
> > +    testpmd>vlan set strip off 1
> > +    testpmd>vlan set filter off 0
> > +    testpmd>vlan set filter off 1
> > +    testpmd>set flush_rx on
> > +
> > +
> > +Test Case 1:     SYN filter
> > +===================================================================
> > +SYN filters might routes TCP packets with their SYN flag set into an
> > assigned queue.  By filtering such packets to an assigned queue,
> security
> > software can monitor and
> > +act on SYN attacks.
> > +
> > +Enable SYN filters with queue 2 on port 0.::
> > +
> > +     testpmd> add_syn_filter 0 priority high queue 2
> > +     testpmd> get_syn_filter 0
> > +If SYN Filter is added successfully,  it displays::
> > +
> > +    syn filter: on, priority: high, queue: 2
> > +Then setup for receive::
> > +
> > +    testpmd> start
> > +Configure the traffic generator to send 5 SYN packets and 5 non-SYN
> > packets .
> > +Reading the stats for port 0 after sending packets.::
> > +
> > +     testpmd> stop
> > +Verify that the packets are received (RX-packets incremented)on the
> queue
> > 2.
> > +Set off SYN filter::
> > +
> > +    testpmd>remove_syn_filter 0
> > +    testpmd>start
> > +Send 5 SYN packets, then reading the stats for port 0 after sending
> > packets.::
> > +
> > +    testpmd> stop
> > +Verify that the packets are not received (RX-packets do not
> increased)on
> > the queue 2 and syn filter is removed.
> > +
> > +
> > +Test Case 2:      5-tuple Filter
> > +===================================================================
> > +This filter identifies specific L3/L4 flows or sets of L3/L4 flows and
> > routes them to dedicated queues. Each filter consists of a 5-tuple
> > (protocol, source and destination IP addresses, source and destination
> > TCP/UDP/SCTP port) and routes packets into one of the Rx queues.
> > +The 5-tuple filters are configured via `dst_ip`, `src_ip`, `dst_port`,
> > `src_port`, `protocol` and Mask.This case supports two type NIC(niantic,
> > 82576), and their command line are different.
> > +Enable the  5-tuple Filter with queue 3 on port 0 for niantic. ::
> > +
> 
> 5-tuple case should cover udp and sctp packets.
> 
> > +    testpmd> add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 1
> > src_port 1 protocol 0x06 mask 0x1f flags 0x0 priority 3 queue 3 index 1
> > +    testpmd> get_5tuple_filter 0 index 1
> > +
> > +Enable the  5-tuple Filter with queue 3 on port 0 for 82576. ::
> > +
> > +    testpmd> add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 1
> > src_port 1 protocol 0x06 mask 0x1f flags 0x02 priority 3 queue 3 index 1
> > +    testpmd> get_5tuple_filter 0 index 1
> > +
> 
> Please explain why flags for 82576 and Niantic have different values.
  Niantic and 82576 the hard register not different, so 82576 need to set the TCP flags. But Niantic not need set.
> > +If L3/L4 5-tuple Filter is added successfully,  it displays::
> > +
> > +    filter[1]:
> > +    Destination IP:  0x02020205    mask: 1
> > +    Source IP:       0x02020204    mask: 1
> > +    Destination Port:       0x0001    mask: 1
> > +    Source Port:       0x0000    mask: 1
> > +    protocol_type: tcp            mask: 1
> > +    priority: 3
> > +Then setup for receive::
> > +
> > +    testpmd> start
> > +If the NIC type is niantic, then send  different type packets such as
> > (`dst_ip`=2.2.2.5 `src_ip`=2.2.2.4 `dst_por`t=1 `src_port`=1
> > `protocol`=tcp) and arp. ::
> > +
> > +    testpmd> stop
> > +Verify that the packets (`dst_ip`=2.2.2.5 `src_ip`=2.2.2.4 `dst_port`=1
> > `src_port`=1 `protocol` `tcp`)or (`dst_ip`=2.2.2.5 `src_ip`=2.2.2.4
> > `dst_port`=1 `src_port`=1 `protocol`=tcp, `flags`=0x2)  are received
> (RX-
> > packets doesn't incremented)on the queue 3.Remove L3/L4 5-tuple  filter.
> > +Disable  5-tuple Filters::
> > +
> > +    testpmd>remove_5tuple_filter 0 index 1
> > +    testpmd>start
> > +Send  packets(`dst_ip`=2.2.2.5 `src_ip`=2.2.2.4 `dst_port`=1
> `src_port`=1
> > `protocol`=tcp) or (`dst_ip`=2.2.2.5 `src_ip`=2.2.2.4 `dst_port`=1
> > `src_port`=1 `protocol`=tcp `flags`=0x2) .Then reading the stats for
> port
> > 0 after sending packets.::
> > +
> > +    testpmd> stop
> > +Verify that the packets are not received (RX-packets do not
> increased)on
> > the queue 3. A 5-bit field that masks each of the fields in the 5-tuple
> > (L4 protocol, IP addresses, TCP/UDP ports).
> > +If  5-tuple fields are masked with 0x0  (`mask`=0x0), the filter will
> > routes all the packets(ip)  on the assigned queue.For instance, enable
> the
> > 5-tuple Filters with queue 3 on port 0 for niantic. however, the value
> of
> > mask is set 0x0::
> > +
> > +    testpmd> add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 1
> > src_port 1 protocol tcp mask 0x0 flags 0x0 priority 3 queue 3 index 1
> > +
> > +
> > +Test Case 3:     ethertype filter
> > +===================================================================
> > +Enable the receipt of  ARP packets with queue 2 on port 0::
> > +
> > +    testpmd> add_ethertype_filter 0 ethertype 0x0806 priority disable 0
> > queue 2 index 1
> > +    testpmd> get_ethertype_filter 0 index 1
> > +If ethertype Filters is added successfully,  it displays::
> > +
> > +    filter[1]:
> > +    ethertype:  0x0806
> > +    priority: disable, 0
> > +    queue: 2
> > +Then setup for receive::
> > +
> > +    testpmd> start
> > +Configure the traffic generator to send 15 ARP packets and 15 non ARP
> > packets.
> > +
> > +    testpmd> stop
> > +Verify that the arp packets are received (RX-packets incremented)on the
> > queue 2 .
> > +remove ethertype filter::
> > +
> > +    testpmd> remove_ethertype_filter 0 index 1
> > +    testpmd> start
> > +Configure the traffic generator to send  15 ARP packets.
> > +
> > +    testpmd> stop
> > +Also, you can change the value of  priority to set a new filter except
> > the case the value of ethertype is 0x0800 with priority enable .The rest
> > of steps are same.
> > +For instance, enable  priority filter(just support niantic)::
> > +
> > +    testpmd> add_ethertype_filter 0 ethertype 0x0806 priority enable 1
> > queue 2 index 1
> > +
> > +Test Case 4:     10GB Multiple filters
> > +===================================================================
> > +Enable ethertype filter, SYN filter and  5-tuple Filter on the port 0
> at
> > same time. Assigning different filters to different queues on port 0::
> > +
> > +    testpmd> add_syn_filter 0 priority high queue 1
> > +    testpmd> add_ethertype_filter 0 ethertype 0x0806 priority disable 0
> > queue 3 index 1
> > +    testpmd> add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 1
> > src_port 1 protocol tcp mask 0x1f priority 3 queue 3 index 1
> > +    testpmd> start
> > +
> 
> Maybe it will be better that each filter redirect packets into different
> queues.
> It will help us check whether each queue act as we expected.
> 
> Is there any case cover the maximum number of queues? We should know the
> value.
> 
   128 queue test case for test assign max queue to received case. but this case will failed,
Because, testpmd not support assign queue received package, I think, when testpmd support assign queue
Received package, I can submit a new test case for test different queue receive package.
> > +Configure the traffic generator to send  different packets. Such as,SYN
> > packets, ARP packets, IP packets and packets with(`dst_ip`=2.2.2.5
> > `src_ip`=2.2.2.4 `dst_port`=1 `src_port`=1 `protocol`=tcp)::
> > +
> > +    testpmd> stop
> > +Verify that different packets are received (RX-packets incremented)on
> the
> > assigned queue.
> > +Remove ethertype filter::
> > +
> > +    testpmd> remove_ethertype_filter 0 index 1
> > +    testpmd>start
> > +Send SYN packets, ARP packets and packets with (`dst_ip`=2.2.2.5
> > `src_ip`=2.2.2.4 `dst_port`=1 `src_port`=1 `protocol`=tcp).::
> > +
> > +    testpmd> stop
> > +Verify that all packets are received (RX-packets incremented)on the
> > assigned queue except arp  packets, remove 5-tuple filter::
> > +
> > +    testpmd>remove_5tuple_filter 0 index 1
> > +    testpmd> start
> > +Send  different packets such as,SYN packets, ARP packets,  packets with
> > (`dst_ip`=2.2.2.5 `src_ip`=2.2.2.4 `dst_port`=1 `src_port`=1
> > `protocol`=tcp)::
> > +
> > +    testpmd>stop
> > +Verify that only SYN packets are received (RX-packets incremented)on
> the
> > assigned queue
> > +set off SYN filter::
> > +
> > +    testpmd>remove_syn_filter 0
> > +    testpmd>start
> > +Configure the traffic generator to send 5 SYN packets.
> > +
> > +    testpmd>stop
> > +Verify that the packets are not received (RX-packets do not
> increased)on
> > the queue 1.
> > +
> > +
> > +Test Case 5:     2-tuple filter
> > +===================================================================
> > +This case is designed for NIC type:I350, 82580.
> > +Enable the receipt of  udp packets with queue 1 on port 0::
> > +
> > +    testpmd> add_2tuple_filter 0 protocol 0x11 1 dst_port 64 1 flags 0
> > priority 3 queue 1 index 1
> > +    testpmd> get_2tuple_filter 0 index 1
> > +If 2-tuple Filter is added successfully,  it displays::
> > +
> > +    filter[1]:
> > +    Destination Port:     0x0040    mask: 1
> > +    protocol:  0x11     mask:1     tcp_flags: 0x00
> > +    priority: 3    queue: 1
> > +Then setup for receive::
> > +
> > +    testpmd> start
> > +Send 15 udp packets(`dst_port`=15, `protocol`=udp) and 15 non udp
> > packets.Reading the stats for port 0 after sending packets::
> > +
> > +    testpmd> stop
> > +
> > +Verify that the udp packets are received (RX-packets incremented)on the
> > queue 1.
> > +Remove 2tuple filter::
> > +
> > +    testpmd> remove_2tuple_filter 0 index 1
> > +    testpmd> start
> > +Configure the traffic generator to send  udp packets(`dst_port`=15,
> > `protocol`=udp).
> > +Reading the stats for port 0 after sending packets::
> > +
> > +    testpmd> stop
> > +Verify that the packets are not received (RX-packets do not
> increased)on
> > the queue 1.
> > +Also, you can change the value of protocol or dstport or flags to set a
> > new filter.the rest of steps are same.For example::
> > +
> 
> Please take care of language syntax.
> 
   Yes, I will review this doc at next version
> > +Enable the receipt of  UDP packets with queue 1 on port 1::
> > +
> > +    testpmd> add_2tuple_filter 1 protocol 0x011 1 dst_port 64 1 flags 0
> > priority 3 queue 2 index 2
> > +
> > +Enable the receipt of  TCP packets with flags on queue 1 of port 1::
> > +
> > +    testpmd> add_2tuple_filter 1 protocol 0x06 1 dst_port 64 1 flags
> 0x3F
> > priority 3 queue 3 index 3
> > +
> > +
> > +Test Case 6: flex filter
> > +===================================================================
> > +This case is designed for NIC type:I350, 82576,82580.
> > +Enable the receipt of   packets(context) with queue 1 on port 0::
> > +
> > +    testpmd> add_flex_filter 0 len 16 bytes
> > 0x0123456789abcdef0000000008060000 mask 000C priority 3 queue 1 index 0
> 
> Please explain the relation of len and mask.
> Has this case been covered the max length of flex filter?
> 
  In flex filter detail info from driver displays as below:
  Value "dword" is a double word type so this mask match "0806"  
> > +    testpmd> get_flex_filter 0 index 0
> > +
> > +If flex Filter is added successfully,  it displays::
> > +    filter[0]:
> > +    length: 16
> > +    dword[]: 0x01234567 89abcdef 00000000 08060000 00000000 00000000
> > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000 00000000
> > +    mask[]:
> >
> 0b000000000000110000000000000000000000000000000000000000000000000000000000
> > 00000000000000000000000000000000000000000000000000000000
> > +    priority: 3    queue: 1
> > +Then setup for receive::
> > +
> > +    testpmd> start
> > +Configure the traffic generator to send  packets(context) and arp
> packtes.
> > +Reading the stats for port 0 after sending packets::
> > +
> > +    testpmd> stop
> > +Verify that the arp packets are received (RX-packets incremented)on the
> > queue 1.
> > +Remove flex filter::
> > +
> > +    testpmd> remove_flex_filter 0 index 0
> > +    testpmd> start
> > +Configure the traffic generator to send packets(context).Reading the
> > stats for port 0 after sending packets::
> > +
> > +    testpmd> stop
> > +Verify that the packets are not received (RX-packets do not
> increased)on
> > the queue 1. Also, you can change the value of length or context or mask
> > to set a new filter.the rest of steps are same.::
> > +
> > +    testpmd> add_flex_filter 0 len 32 bytes
> > 0x0123456789abcdef00000000080600000123456789abcdef0000000008060000 mask
> > 000C000C priority 1 queue 2 index 7
> > +
> > +Test Case 7: priority filter
> > +===================================================================
> > +This case is designed for NIC (niantic,I350, 82576 and 82580). If
> packets
> > are match on  different filters with same type, the filter with high
> > priority will be receive packets. For example, packets are match on two
> > five-tuple filters with different priority, the filter with high
> priority
> > will be receive packets. if packets are match on  different filters with
> > different type, packets based on the above criteria and the following
> > order.when syn set priority high, syn filter has highest priority than
> > others filter. And flex filter has higher priority than 2-tuple filter.
> > +If the Nic is niantic, enable the 5-tuple filter::
> > +
> > +    testpmd> add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 1
> > src_port 1 protocol 0x06 mask 0x1f flags 0x0 priority 2 queue 2 index 1
> > +    testpmd> add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 2
> > src_port 2 protocol 0x06 mask 0x18 flags 0x0 priority 3 queue 3 index 2
> > +    testpmd> start
> > +Configure the traffic generator to send  packets (`dst_ip`=2.2.2.5
> > `src_ip`=2.2.2.4 `dst_port`=1 `src_port`=1 `protocol`=tcp).
> > +
> > +    testpmd> stop
> > +packets are received (RX-packets be increased)on the queue 2.
> > +Remove the 5tuple filter with high priority::
> > +
> > +    testpmd>remove_5tuple_filter 0 index 1
> > +    testpmd> start
> > +Configure the traffic generator to send  packets (`dst_ip`=2.2.2.5
> > `src_ip`=2.2.2.4 `dst_port`=1 `src_port`=1 `protocol`=tcp)
> > +
> > +    testpmd> stop
> > +packets are received (RX-packets be increased)on the queue 3.
> > +If the Nic is I350 or 82580, enable the 2-tuple  and flex filters::
> > +
> > +    testpmd> add_flex_filter 0 len 16 bytes
> > 0x0123456789abcdef0000000008000000 mask 000C priority 2 queue 1 index 0
> > +    testpmd> add_2tuple_filter 0 protocol 0x11 1 dst_port 64 1 flags 0
> > priority 3 queue 2 index 1
> > +    testpmd> start
> > +Configure the traffic generator to send  packets (`dst_ip`=2.2.2.5
> > `src_ip`=2.2.2.4 `dst_port`=64 `src_port`=1 `protocol`=udp).
> > +
> > +    testpmd> stop
> > +packets are received (RX-packets be increased)on the queue 2.
> > +Remove the 2tuple filter with high priority::
> > +
> > +    testpmd>remove_2tuple_filter 0 index 1
> > +    testpmd> start
> > +Configure the traffic generator to send  packets (`dst_ip`=2.2.2.5
> > `src_ip`=2.2.2.4 `dst_port`=64 `src_port`=1 `protocol`=udp),
> > +
> > +    testpmd> stop
> > +packets are received (RX-packets be increased)on the queue 1.
> > +If the Nic is 82576, enable the syn and 2-tuple filter::
> > +
> > +    testpmd>add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 1
> > src_port 1 protocol 0x06 mask 0x1f flags 0x02 priority 3 queue 3 index 1
> > +    testpmd>add_syn_filter 0 priority high queue 2
> > +    testpmd> start
> > +Configure the traffic generator to send  packets (`dst_ip`=2.2.2.5
> > `src_ip`=2.2.2.4 `dst_port`=1 `src_port`=1 `protocol`=tcp `flags`="S").
> > +
> > +    testpmd>stop
> > +packets are received (RX-packets be increased)on the queue 2.
> > +Remove the syn filter with high priority::
> > +
> > +    testpmd>remove_syn_filter 0
> > +    testpmd>start
> > +Configure the traffic generator to send  packets (`dst_ip`=2.2.2.5
> > `src_ip`=2.2.2.4 `dst_port`=64 `src_port`=1 `protocol`=tcp `flags`="S").
> > +
> > +    testpmd> stop
> > +packets are received (RX-packets be increased)on the queue 3.
> > +
> > +
> > +
> > +Test Case 8: 1GB Multiple filters
> > +===================================================================
> > +This case is designed for NIC(I350, 82576,82580). Enable syn filter and
> > ethertype filter on the port 0 at the same time.  Assigning different
> > filters to different queues on port 0.Enable the filters::
> > +
> > +    testpmd> add_syn_filter 0 priority high queue 1
> > +    testpmd> add_ethertype_filter 0 ethertype 0x0806 priority disable 0
> > queue 3 index 1
> > +    testpmd> start
> > +
> > +Configure the traffic generator to send ethertype packets and arp
> > packets . ::
> > +
> > +    testpmd> stop
> > +Then Verify that the packet are received on the queue 1,queue 3.
> > +Remove all the filter::
> > +
> > +    testpmd> remove_syn_filter 0
> > +    testpmd> remove_ethertype_filter 0 index 1
> > +
> > +Configure the traffic generator to send udp packets and arp packets.
> Then
> > Verify that the packet are not received on the queue 1 and queue 3 ::
> > +
> > +    testpmd> quit
> > +
> > +Test Case 9: jumbo framesize filter
> > +===================================================================
> > + This case is designed for NIC (niantic,I350, 82576 and 82580). Since
> > ``Testpmd`` could transmits packets with jumbo frame size , it also
> could
> > transmit above packets on assigned queue.
> > +Launch the app ``testpmd`` with the following arguments::
> > +
> > +    testpmd -c ffff -n 4 -- -i --disable-rss --rxq=4 --txq=4 --nb-
> cores=8
> > --nb-ports=2 --rxd=1024 --txd=1024 --burst=144 --txpt=32 --txht=8 --
> txwt=0
> > --txfreet=0 --rxfreet=64 --mbcache=200 --mbuf-size=2048 --max-pkt-
> len=9600
> > +
> > +    testpmd>set stat_qmap rx 0 0 0
> > +    testpmd>set stat_qmap rx 0 1 1
> > +    testpmd>set stat_qmap rx 0 2 2
> > +    testpmd>vlan set strip off 0
> > +    testpmd>vlan set strip off 1
> > +    testpmd>vlan set filter off 0
> > +    testpmd>vlan set filter off 1
> > +Enable the syn filters with large size::
> > +
> > +    testpmd> add_syn_filter 0 priority high queue 1
> > +    testpmd> start
> > +
> > +Configure the traffic generator to send syn packets(framesize=2000) . ::
> > +
> > +    testpmd> stop
> > +Then Verify that the packet are received on the queue 1.
> > +Remove  the filter::
> > +
> > +    testpmd> remove_syn_filter 0
> > +
> > +Configure the traffic generator to send syn packets and s. Then Verify
> > that the packet are not received on the queue 1   ::
> > +
> > +    testpmd> quit
> > +
> > +Test Case 10: 128 queues
> > +===================================================================
> > +This case is designed for NIC(niantic). Since NIC(niantic) has 128
> > transmit queues, it should be supports  128 kinds of filter if Hardware
> > have enough cores.
> > +Launch the app ``testpmd`` with the following arguments::
> > +
> > +    ./testpmd -c fffff -n 4 -- -i --disable-rss --rxq=128 --txq=128 --
> nb-
> > cores=16 --nb-ports=2 --total-num-mbufs=60000
> > +
> > +    testpmd>set stat_qmap rx 0 0 0
> > +    testpmd>set stat_qmap rx 0 64 1
> > +    testpmd>set stat_qmap rx 0 64 2
> 
> Here should be queue 127?
> > +    testpmd>vlan set strip off 0
> > +    testpmd>vlan set strip off 1
> > +    testpmd>vlan set filter off 0
> > +    testpmd>vlan set filter off 1
> > +Enable the  5-tuple Filters with different queues (64,127) on port 0
> for
> > niantic. ::
> > +
> > +    testpmd> add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 1
> > src_port 1 protocol 0x06 mask 0x1f flags 0x0 priority 3 queue 64 index 1
> > +    testpmd> add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 2
> > src_port 1 protocol 0x06 mask 0x1f flags 0x0 priority 3 queue 127 index
> 1
> > +Send  packets(`dst_ip`=2.2.2.5 `src_ip`=2.2.2.4 `dst_port`=1
> `src_port`=1
> > `protocol`=tcp) and (`dst_ip`=2.2.2.5 `src_ip`=2.2.2.4 `dst_port`=2
> > `src_port`=1 `protocol`=tcp ) . Then reading the stats for port 0 after
> > sending packets. packets are received on the queue 64 and queue 127
> > + When setting 5-tuple Filter with queue(128), it will display failure
> > because the number of queues no more than 128.
> > +
> > +
> > +
> > +Test Case 11: 10G NIC Performance
> > +===================================================================
> > +This case is designed for Niantic. It provides the performance data
> with
> > and without  generic filter. ::
> > +Launch app without filter:
> > +    ./testpmd -c fffff -n 4 -- -i --disable-rss --rxq=4 --txq=4 --nb-
> > cores=16 --nb-ports=2
> > +    testpmd> start
> > +
> > +Send the packets stream from packet generator::
> > +
> > +    testpmd> quit
> > +Enable the filters on app::
> > +
> > +    ./testpmd -c fffff -n 4 -- -i --disable-rss --rxq=4 --txq=4 --nb-
> > cores=16 --nb-ports=2
> > +
> > +    testpmd>set stat_qmap rx 0 0 0
> > +    testpmd>set stat_qmap rx 0 1 1
> > +    testpmd>set stat_qmap rx 0 2 2
> > +    testpmd>set stat_qmap rx 0 3 3
> > +    testpmd>set flush_rx on
> > +    testpmd> add_syn_filter 0 priority high queue 1
> > +    testpmd> add_ethertype_filter 0 ethertype 0x0806 priority disable 0
> > queue 2 index 1
> > +    testpmd> add_5tuple_filter 0 dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port
> 1
> > src_port 1 protocol 0x06 mask 0x1f flags 0x02 priority 3 queue 3 index 1
> > +    testpmd> start
> > +
> 
> Please explain why add three filters here.  This case mixed three
> different types of filter, it's hard to measure performance drop of every
> filter.
> It's better to enlarge performance measure scope as list below.
> 
This case compare enable and disable filter performance, we will send three stream for every filter performance compare 
> Disable all generic filter
> Enable sync filter
> Enable ethertype filter
> Enable one 5tuple filter
> ...
> Several samples between maximum.
> ...
> Enable maximum 5tuple filter
> 
> 
> > +Send the packets stream from packet generator::
> > +
> > +    testpmd> quit
> > +
> > +
> > +
> > ++-------+---------+---------+
> > +| Frame | disable | enable  |
> > +| Size  | filter  | filter  |
> > ++-------+---------+---------+
> > +|  64   |         |         |
> > ++-------+---------+---------+
> > +|  128  |         |         |
> > ++-------+---------+---------+
> > +|  256  |         |         |
> > ++-------+---------+---------+
> > +|  512  |         |         |
> > ++-------+---------+---------+
> > +|  1024 |         |         |
> > ++-------+---------+---------+
> > +|  1280 |         |         |
> > ++-------+---------+---------+
> > +|  1518 |         |         |
> > ++-------+---------+---------+
> > +
> > +
> > +Test Case 12: 1G NIC Performance
> > +===================================================================
> > +This case is designed for NIC (I350, 82580, and 82576). It provides the
> > performance data with and without  generic filter.::
> > +
> > +    ./testpmd -c fffff -n 4 -- -i --disable-rss --rxq=4 --txq=4 --nb-
> > cores=16 --nb-ports=2
> > +    testpmd> start
> > +
> > +Send the packets stream from packet generator::
> > +
> > +    testpmd> quit
> > +
> > +Enable the filter ::
> > +
> > +    ./testpmd -c fffff -n 4 -- -i --disable-rss --rxq=4 --txq=4 --nb-
> > cores=16 --nb-ports=2
> > +
> > +    testpmd>set stat_qmap rx 0 0 0
> > +    testpmd>set stat_qmap rx 0 1 1
> > +    testpmd>set stat_qmap rx 0 2 2
> > +    testpmd>set stat_qmap rx 0 3 3
> > +    testpmd>set flush_rx on
> > +    testpmd> add_syn_filter 0 priority high queue 1
> > +    testpmd> add_ethertype_filter 0 ethertype 0x0806 priority disable 0
> > queue 2 index 1
> > +    testpmd> start
> > +
> > +
> > +Send the packets stream from packet generator::
> > +
> > +    testpmd> quit
> > +
> 
> Same as above.
> It's better to enlarge performance measure scope.
> 
> > +
> > +
> > ++-------+---------+---------+
> > +| Frame | disable | enable  |
> > +| Size  | filter  | filter  |
> > ++-------+---------+---------+
> > +|  64   |         |         |
> > ++-------+---------+---------+
> > +|  128  |         |         |
> > ++-------+---------+---------+
> > +|  256  |         |         |
> > ++-------+---------+---------+
> > +|  512  |         |         |
> > ++-------+---------+---------+
> > +|  1024 |         |         |
> > ++-------+---------+---------+
> > +|  1280 |         |         |
> > ++-------+---------+---------+
> > +|  1518 |         |         |
> > ++-------+---------+---------+
> > --
> > 1.7.4.4


  reply	other threads:[~2015-05-26  5:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25  8:54 [dts] [dts 1/4] [PATCH V1] add generic_filter test for niantic NIC huilong,xu
2015-05-25  8:54 ` [dts] [dts 2/4] [PATCH V1] add generic_filter test for fortville NIC huilong,xu
2015-05-25  8:59   ` Liu, Yong
2015-05-25  9:15     ` Xu, HuilongX
2015-05-26  1:29       ` Liu, Yong
2015-05-25  8:54 ` [dts] [dts 3/4] [PATCH V1] add generic_filter test plan huilong,xu
2015-05-26  2:11   ` Liu, Yong
2015-05-26  5:33     ` Xu, HuilongX [this message]
2015-05-25  8:54 ` [dts] [dts 4/4] [PATCH V1] add generic filter huilong,xu

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=DF2A19295B96364286FEB7F3DDA27A4601112DCB@SHSMSX101.ccr.corp.intel.com \
    --to=huilongx.xu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yong.liu@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).