get:
Show a patch.

patch:
Update a patch.

put:
Update a patch.

GET /api/patches/103917/?format=api
HTTP 200 OK
Allow: GET, PUT, PATCH, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 103917,
    "url": "http://patches.dpdk.org/api/patches/103917/?format=api",
    "web_url": "http://patches.dpdk.org/project/dts/patch/20211108135846.95769-2-yanx.xia@intel.com/",
    "project": {
        "id": 3,
        "url": "http://patches.dpdk.org/api/projects/3/?format=api",
        "name": "DTS",
        "link_name": "dts",
        "list_id": "dts.dpdk.org",
        "list_email": "dts@dpdk.org",
        "web_url": "",
        "scm_url": "git://dpdk.org/tools/dts",
        "webscm_url": "http://git.dpdk.org/tools/dts/",
        "list_archive_url": "https://inbox.dpdk.org/dts",
        "list_archive_url_format": "https://inbox.dpdk.org/dts/{}",
        "commit_url_format": ""
    },
    "msgid": "<20211108135846.95769-2-yanx.xia@intel.com>",
    "list_archive_url": "https://inbox.dpdk.org/dts/20211108135846.95769-2-yanx.xia@intel.com",
    "date": "2021-11-08T13:58:44",
    "name": "[V1,1/3] test_plan/generic_filter: delete generic_filter_test_plan",
    "commit_ref": null,
    "pull_url": null,
    "state": "accepted",
    "archived": false,
    "hash": "125caa280c4231354b1eb1ab7dc6b335062ee963",
    "submitter": {
        "id": 2034,
        "url": "http://patches.dpdk.org/api/people/2034/?format=api",
        "name": "Yan Xia",
        "email": "yanx.xia@intel.com"
    },
    "delegate": null,
    "mbox": "http://patches.dpdk.org/project/dts/patch/20211108135846.95769-2-yanx.xia@intel.com/mbox/",
    "series": [
        {
            "id": 20366,
            "url": "http://patches.dpdk.org/api/series/20366/?format=api",
            "web_url": "http://patches.dpdk.org/project/dts/list/?series=20366",
            "date": "2021-11-08T13:58:43",
            "name": "*** delete generic_filter ***",
            "version": 1,
            "mbox": "http://patches.dpdk.org/series/20366/mbox/"
        }
    ],
    "comments": "http://patches.dpdk.org/api/patches/103917/comments/",
    "check": "pending",
    "checks": "http://patches.dpdk.org/api/patches/103917/checks/",
    "tags": {},
    "related": [],
    "headers": {
        "Return-Path": "<dts-bounces@dpdk.org>",
        "X-Original-To": "patchwork@inbox.dpdk.org",
        "Delivered-To": "patchwork@inbox.dpdk.org",
        "Received": [
            "from mails.dpdk.org (mails.dpdk.org [217.70.189.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id 42D51A0C4B;\n\tMon,  8 Nov 2021 06:56:59 +0100 (CET)",
            "from [217.70.189.124] (localhost [127.0.0.1])\n\tby mails.dpdk.org (Postfix) with ESMTP id 62C4740E5A;\n\tMon,  8 Nov 2021 06:56:58 +0100 (CET)",
            "from mga04.intel.com (mga04.intel.com [192.55.52.120])\n by mails.dpdk.org (Postfix) with ESMTP id AD03540E5A\n for <dts@dpdk.org>; Mon,  8 Nov 2021 06:56:55 +0100 (CET)",
            "from orsmga004.jf.intel.com ([10.7.209.38])\n by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;\n 07 Nov 2021 21:56:55 -0800",
            "from unknown (HELO dpdk.lan) ([10.240.183.77])\n by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;\n 07 Nov 2021 21:56:53 -0800"
        ],
        "X-IronPort-AV": [
            "E=McAfee;i=\"6200,9189,10161\"; a=\"230885732\"",
            "E=Sophos;i=\"5.87,217,1631602800\"; d=\"scan'208\";a=\"230885732\"",
            "E=Sophos;i=\"5.87,217,1631602800\"; d=\"scan'208\";a=\"601300611\""
        ],
        "From": "Yan Xia <yanx.xia@intel.com>",
        "To": "dts@dpdk.org",
        "Cc": "Yan Xia <yanx.xia@intel.com>",
        "Date": "Mon,  8 Nov 2021 13:58:44 +0000",
        "Message-Id": "<20211108135846.95769-2-yanx.xia@intel.com>",
        "X-Mailer": "git-send-email 2.33.1",
        "In-Reply-To": "<20211108135846.95769-1-yanx.xia@intel.com>",
        "References": "<20211108135846.95769-1-yanx.xia@intel.com>",
        "MIME-Version": "1.0",
        "Content-Transfer-Encoding": "8bit",
        "Subject": "[dts] [PATCH V1 1/3] test_plan/generic_filter: delete\n generic_filter_test_plan",
        "X-BeenThere": "dts@dpdk.org",
        "X-Mailman-Version": "2.1.29",
        "Precedence": "list",
        "List-Id": "test suite reviews and discussions <dts.dpdk.org>",
        "List-Unsubscribe": "<https://mails.dpdk.org/options/dts>,\n <mailto:dts-request@dpdk.org?subject=unsubscribe>",
        "List-Archive": "<http://mails.dpdk.org/archives/dts/>",
        "List-Post": "<mailto:dts@dpdk.org>",
        "List-Help": "<mailto:dts-request@dpdk.org?subject=help>",
        "List-Subscribe": "<https://mails.dpdk.org/listinfo/dts>,\n <mailto:dts-request@dpdk.org?subject=subscribe>",
        "Errors-To": "dts-bounces@dpdk.org",
        "Sender": "\"dts\" <dts-bounces@dpdk.org>"
    },
    "content": "delete generic_filter because of these types of filter removed,\nrelated dpdk commit-id:\nae42875d6 ethdev: remove legacy SYN filter type support\n92067db05 ethdev: remove legacy N-tuple filter type support\n2be70bcdb ethdev: remove legacy flexible filter type support\n35b1c68af ethdev: remove legacy EtherType filter type support\n\nSigned-off-by: Yan Xia <yanx.xia@intel.com>\n---\n test_plans/generic_filter_test_plan.rst | 398 ------------------------\n 1 file changed, 398 deletions(-)\n delete mode 100644 test_plans/generic_filter_test_plan.rst",
    "diff": "diff --git a/test_plans/generic_filter_test_plan.rst b/test_plans/generic_filter_test_plan.rst\ndeleted file mode 100644\nindex e35d0381..00000000\n--- a/test_plans/generic_filter_test_plan.rst\n+++ /dev/null\n@@ -1,398 +0,0 @@\n-.. Copyright (c) <2015-2017>, Intel Corporation\n-   All rights reserved.\n-\n-   Redistribution and use in source and binary forms, with or without\n-   modification, are permitted provided that the following conditions\n-   are met:\n-\n-   - Redistributions of source code must retain the above copyright\n-     notice, this list of conditions and the following disclaimer.\n-\n-   - Redistributions in binary form must reproduce the above copyright\n-     notice, this list of conditions and the following disclaimer in\n-     the documentation and/or other materials provided with the\n-     distribution.\n-\n-   - Neither the name of Intel Corporation nor the names of its\n-     contributors may be used to endorse or promote products derived\n-     from this software without specific prior written permission.\n-\n-   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS\n-   \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT\n-   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS\n-   FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE\n-   COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,\n-   INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES\n-   (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR\n-   SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)\n-   HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,\n-   STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)\n-   ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED\n-   OF THE POSSIBILITY OF SUCH DAMAGE.\n-\n-====================\n-Generic Filter Tests\n-====================\n-\n-\n-Description\n-===========\n-\n-This document provides the plan for testing the generic filter feature of\n-10GbE and 1GbE Ethernet Controller.In `testpmd`, app provides Generic Filter\n-API to manage filter rules for kinds of packets, and calls the API to manage\n-HW filters in HW, or SW filters in SW table.\n-\n-* A generic filter provides an ability to identify specific flows or sets of\n-  flows and routes them to dedicated queues.\n-* Based on the Generic Filter mechanism, all the SYN packets are placed in an\n-  assigned queue.\n-* Based on the Generic Filter mechanism, all packets belonging to L3/L4 flows\n-  to be placed in a specific HW queue.Each filter consists of a 5-tuple\n-  (protocol, source and destination IP addresses, source and destination\n-  TCP/UDP/SCTP port) and routes packets into one of the Rx queues\n-* L2 Ethertype Filters provides an ability to identify packets by their L2\n-  Ethertype and assigns them to receive queues.  `Testpmd` app is used to test\n-  all types of HW filters. Case 1~9 are the function test for the above app\n-  while case 11-12 are the performance test for Niantic, I350, 82580 and\n-  82576.\n-\n-\n-Prerequisites\n-=============\n-\n-Assuming that ports ``0`` and ``1`` are connected to a traffic generator's port ``A`` and ``B``.\n-\n-Setup for ``testpmd``\n----------------------\n-\n-Launch the app ``testpmd`` with the following arguments::\n-\n-    ./testpmd -c fffff -n 4 -- -i --disable-rss --rxq=4 --txq=4 --nb-cores=16 --nb-ports=2\n-\n-The -n command is used to select the number of memory channels. It should be\n-matched with the number of memory channels on that setup. The value of rxq and\n-txq is 1 by default, it's necessary to increase them, and make sure rxq and\n-txq more than one. At the same time rss is enable by default, so disable\n-it. Map port queues to statistic counter registers. Fortville not support this\n-function::\n-\n-    testpmd>set stat_qmap rx 0 0 0\n-    testpmd>set stat_qmap rx 0 1 1\n-    testpmd>set stat_qmap rx 0 2 2\n-    testpmd>set stat_qmap rx 0 3 3\n-\n-Setup for receive all packet and disable vlan strip function::\n-\n-    testpmd>vlan set strip off 0\n-    testpmd>vlan set strip off 1\n-    testpmd>vlan set filter off 0\n-    testpmd>vlan set filter off 1\n-    testpmd>set flush_rx on\n-\n-\n-Test Case 1:     SYN filter\n-===========================\n-\n-SYN filters might routes TCP packets with their SYN flag set into an assigned\n-queue.  By filtering such packets to an assigned queue, security software can\n-monitor and act on SYN attacks.\n-\n-Enable SYN filters with queue 2 on port 0::\n-\n-     testpmd> syn_filter 0 add priority high queue 2\n-\n-Then setup for receive::\n-\n-    testpmd> start\n-\n-Configure the traffic generator to send 5 SYN packets and 5 non-SYN packets .\n-Reading the stats for port 0 after sending packets::\n-\n-     testpmd> stop\n-\n-Verify that the packets are received (RX-packets incremented)on the queue 2.\n-Set off SYN filter::\n-\n-    testpmd>syn_filter 0 del priority high queue 2\n-    testpmd>start\n-\n-Send 5 SYN packets, then reading the stats for port 0 after sending packets::\n-\n-    testpmd> stop\n-\n-Verify that the packets are not received (RX-packets do not increased)on the queue 2 and syn filter is removed.\n-\n-\n-Test Case 2:      5-tuple Filter\n-===================================================================\n-\n-This filter identifies specific L3/L4 flows or sets of L3/L4 flows and routes\n-them to dedicated queues. Each filter consists of a 5-tuple (protocol, source\n-and destination IP addresses, source and destination TCP/UDP/SCTP port) and\n-routes packets into one of the Rx queues.  The 5-tuple filters are configured\n-via `dst_ip`, `src_ip`, `dst_port`, `src_port`, `protocol` and Mask.This case\n-supports two type NIC(niantic, 82576), and their command line are\n-different. niantic and 82576 register are different, for niantic TCP flags not\n-need config,so used 0, 82576 must config tcp flags, the tcp flags means the\n-package is a SYN package.  Enable the 5-tuple Filter with queue 3 on port 0\n-for niantic::\n-\n-    testpmd> 5tuple_filter 0 add dst_ip 2.2.2.5 src_ip 2.2.2.4 dst_port 1 src_port 1 protocol 0x06 mask 0x1f tcp_flags 0x0 priority 3 queue 3\n-\n-Enable the  5-tuple Filter with queue 3 on port 0 for 82576::\n-\n-    testpmd> 5tuple_filter 0 add 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\n-\n-Then setup for receive::\n-\n-    testpmd> start\n-\n-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_port` = 1 `src_port` = 1 `protocol` = tcp) and arp::\n-\n-    testpmd> stop\n-\n-Verify that the packets (`dst_ip` = 2.2.2.5 `src_ip` = 2.2.2.4 `dst_port` = 1\n-`src_port` = 1 `protocol` = tcp)or (`dst_ip` = 2.2.2.5 `src_ip` = 2.2.2.4\n-`dst_port` = 1 `src_port` = 1 `protocol` = tcp, `flags` = 0x2) are received\n-(RX-packets doesn't incremented)on the queue 3.Remove L3/L4 5-tuple filter.\n-Disable 5-tuple Filters::\n-\n-    testpmd> 5tuple_filter 0 del 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\n-    testpmd> start\n-\n-Send packets(`dst_ip` = 2.2.2.5 `src_ip` = 2.2.2.4 `dst_port` = 1 `src_port` =\n-1 `protocol` = tcp) or (`dst_ip` = 2.2.2.5 `src_ip` = 2.2.2.4 `dst_port` = 1\n-`src_port` = 1 `protocol` = tcp `flags` = 0x2). Then reading the stats for\n-port 0 after sending packets::\n-\n-    testpmd> stop\n-\n-Verify that the packets are not received (RX-packets do not increased)on the\n-queue 3. A 5-bit field that masks each of the fields in the 5-tuple (L4\n-protocol, IP addresses, TCP/UDP ports).  If 5-tuple fields are masked with 0x0\n-(`mask` = 0x0), the filter will routes all the packets(ip) on the assigned\n-queue.For instance, enable the 5-tuple Filters with queue 3 on port 0 for\n-niantic. however, the value of mask is set 0x0::\n-\n-    testpmd> 5tuple_filter 0 add 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\n-\n-Test Case 3:     ethertype filter\n-=================================\n-\n-Enable the receipt of  ARP packets with queue 2 on port 0::\n-\n-    testpmd> ethertype_filter 0 add ethertype 0x0806 priority disable 0 queue 2\n-\n-Then setup for receive::\n-\n-    testpmd> start\n-\n-Configure the traffic generator to send 15 ARP packets and 15 non ARP packets::\n-\n-    testpmd> stop\n-\n-Verify that the arp packets are received (RX-packets incremented)on the queue\n-2 .  remove ethertype filter::\n-\n-    testpmd> ethertype_filter 0 del ethertype 0x0806 priority disable 0 queue 2\n-    testpmd> start\n-\n-Configure the traffic generator to send  15 ARP packets.\n-\n-    testpmd> stop\n-\n-Also, you can change the value of priority to set a new filter except the case\n-the value of ethertype is 0x0800 with priority enable .The rest of steps are\n-same.\n-\n-For instance, enable priority filter(just support niantic)::\n-\n-    testpmd> ethertype_filter 0 add ethertype 0x0806 priority enable 1 queue 2\n-\n-Test Case 5:     2-tuple filter\n-===============================\n-\n-This case is designed for NIC type:I350, 82580.  Enable the receipt of udp\n-packets with queue 1 on port 0::\n-\n-    testpmd> 2tuple_filter 0 add protocol 0x11 1 dst_port 64 1 flags 0 priority 3 queue 1\n-\n-Then setup for receive::\n-\n-    testpmd> start\n-\n-Send 15 udp packets(`dst_port` = 15, `protocol` = udp) and 15 non udp\n-packets. Reading the stats for port 0 after sending packets::\n-\n-    testpmd> stop\n-\n-Verify that the udp packets are received (RX-packets incremented)on the\n-queue 1.  Remove 2tuple filter::\n-\n-    testpmd> 2tuple_filter 0 del protocol 0x11 1 dst_port 64 1 flags 0 priority 3 queue 1\n-    testpmd> start\n-\n-Configure the traffic generator to send udp packets(`dst_port` = 15,\n-`protocol` = udp).  Reading the stats for port 0 after sending packets::\n-\n-    testpmd> stop\n-\n-Verify that the packets are not received (RX-packets do not increased)on the\n-queue 1.  Also, you can change the value of protocol or dstport or flags to\n-set a new filter.the rest of steps are same. For example:\n-\n-Enable the receipt of  UDP packets with queue 1 on port 1::\n-\n-    testpmd> 2tuple_filter 1 add protocol 0x011 1 dst_port 64 1 flags 0 priority 3 queue 2\n-\n-Enable the receipt of  TCP packets with flags on queue 1 of port 1::\n-\n-    testpmd> 2tuple_filter 1 add protocol 0x06 1 dst_port 64 1 flags 0x3F priority 3 queue 3\n-\n-\n-Test Case 6: flex filter\n-========================\n-\n-This case is designed for NIC type:I350, 82576,82580.  Enable the receipt of\n-packets(context) with queue 1 on port 0::\n-\n-    testpmd> flex_filter 0 add len 16 bytes 0x0123456789abcdef0000000008060000 mask 000C priority 3 queue 1\n-\n-If flex Filter is added successfully,  it displays::\n-\n-    bytes[0]:01 bytes[1]:23 bytes[2]:45 bytes[3]:67 bytes[4]:89 bytes[5]:ab bytes[6]:cd bytes[7]:ef bytes[8]:00 bytes[9]:00 bytes[10]:00 bytes[11]:00 bytes[12]:08 bytes[13]:06 bytes[14]:00 bytes[15]:00\n-    mask[0]:00 mask[1]:0c\n-\n-Then setup for receive::\n-\n-    testpmd> start\n-\n-Configure the traffic generator to send packets(context) and arp packets.\n-Reading the stats for port 0 after sending packets::\n-\n-    testpmd> stop\n-\n-Verify that the arp packets are received (RX-packets incremented)on the\n-queue 1.  Remove flex filter::\n-\n-    testpmd> flex_filter 0 add len 16 bytes 0x0123456789abcdef0000000008060000 mask 000C priority 3 queue 1\n-    testpmd> start\n-\n-Configure the traffic generator to send packets(context).Reading the stats for\n-port 0 after sending packets::\n-\n-    testpmd> stop\n-\n-Verify that the packets are not received (RX-packets do not increased)on the\n-queue 1. Also, you can change the value of length or context or mask to set a\n-new filter.the rest of steps are same::\n-\n-    testpmd> flex_filter 0 add len 32 bytes 0x0123456789abcdef00000000080600000123456789abcdef0000000008060000 mask 000C000C priority 1 queue 2\n-\n-Test Case 7: priority filter\n-============================\n-\n-This case is designed for NIC (niantic,I350, 82576 and 82580). If packets are\n-match on different filters with same type, the filter with high priority will\n-be receive packets. For example, packets are match on two five-tuple filters\n-with different priority, the filter with high priority will be receive\n-packets. if packets are match on different filters with different type,\n-packets based on the above criteria and the following order.when syn set\n-priority high, syn filter has highest priority than others filter. And flex\n-filter has higher priority than 2-tuple filter.  If the Nic is niantic, enable\n-the 5-tuple filter::\n-\n-    testpmd> 5tuple_filter 0 add 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\n-    testpmd> 5tuple_filter 0 add 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\n-    testpmd> start\n-\n-Configure the traffic generator to send packets (`dst_ip` = 2.2.2.5 `src_ip` =\n-2.2.2.4 `dst_port` = 1 `src_port` = 1 `protocol` = tcp).\n-\n-    testpmd> stop\n-\n-packets are received (RX-packets be increased)on the queue 2.  Remove the\n-5tuple filter with high priority::\n-\n-    testpmd>5tuple_filter 0 del 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\n-    testpmd> start\n-\n-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)\n-\n-    testpmd> stop\n-\n-packets are received (RX-packets be increased)on the queue 3.  If the Nic is\n-I350 or 82580, enable the 2-tuple and flex filters::\n-\n-    testpmd> flex_filter 0 add len 16 bytes 0x0123456789abcdef0000000008000000 mask 000C priority 2 queue 1\n-    testpmd> 2tuple_filter 0 add protocol 0x11 1 dst_port 64 1 flags 0 priority 3 queue 2\n-    testpmd> start\n-\n-Configure the traffic generator to send packets (`dst_ip` = 2.2.2.5 `src_ip` =\n-2.2.2.4 `dst_port` = 64 `src_port` = 1 `protocol` = udp).\n-\n-    testpmd> stop\n-\n-packets are received (RX-packets be increased)on the queue 2.  Remove the\n-2tuple filter with high priority::\n-\n-    testpmd> 2tuple_filter 0 add protocol 0x11 1 dst_port 64 1 flags 0 priority 3 queue 2\n-    testpmd> start\n-\n-Configure the traffic generator to send packets (`dst_ip` = 2.2.2.5 `src_ip` =\n-2.2.2.4 `dst_port` = 64 `src_port` = 1 `protocol` = udp),\n-\n-    testpmd> stop\n-\n-packets are received (RX-packets be increased)on the queue 1.  If the Nic is\n-82576, enable the syn and 2-tuple filter::\n-\n-    testpmd>5tuple_filter 0 add 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\n-    testpmd>syn_filter 0 add priority high queue 2\n-    testpmd> start\n-\n-Configure the traffic generator to send packets (`dst_ip` = 2.2.2.5 `src_ip` =\n-2.2.2.4 `dst_port` = 1 `src_port` = 1 `protocol` = tcp `flags` = \"S\").\n-\n-    testpmd>stop\n-\n-packets are received (RX-packets be increased)on the queue 2.  Remove the syn\n-filter with high priority::\n-\n-    testpmd>syn_filter 0 del priority high queue 2\n-    testpmd>start\n-\n-Configure the traffic generator to send packets (`dst_ip` = 2.2.2.5 `src_ip` =\n-2.2.2.4 `dst_port` = 64 `src_port` = 1 `protocol` = tcp `flags` = \"S\").\n-\n-    testpmd> stop\n-\n-packets are received (RX-packets be increased)on the queue 3.\n-\n-\n-Test Case 8: 1GB Multiple filters\n-=================================\n-\n-This case is designed for NIC(I350, 82576,82580). Enable syn filter and\n-ethertype filter on the port 0 at the same time.  Assigning different filters\n-to different queues on port 0.Enable the filters::\n-\n-    testpmd> syn_filter 0 add priority high queue 1\n-    testpmd> ethertype_filter 0 add ethertype 0x0806 priority disable 0 queue 3\n-    testpmd> start\n-\n-Configure the traffic generator to send ethertype packets and arp packets::\n-\n-    testpmd> stop\n-\n-Then Verify that the packet are received on the queue 1,queue 3.  Remove all\n-the filter::\n-\n-    testpmd> syn_filter 0 add priority high queue 1\n-    testpmd> ethertype_filter 0 add ethertype 0x0806 priority disable 0 queue 3\n-\n-Configure the traffic generator to send udp packets and arp packets. Then\n-Verify that the packet are not received on the queue 1 and queue 3::\n-\n-    testpmd> quit\n",
    "prefixes": [
        "V1",
        "1/3"
    ]
}