Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/104814/?format=api
http://patchwork.dpdk.org/api/patches/104814/?format=api", "web_url": "http://patchwork.dpdk.org/project/dts/patch/20211202111453.146572-1-yanx.xia@intel.com/", "project": { "id": 3, "url": "http://patchwork.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": "<20211202111453.146572-1-yanx.xia@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dts/20211202111453.146572-1-yanx.xia@intel.com", "date": "2021-12-02T11:14:51", "name": "[V3,1/3] test_plans/fortville_rss_granularity_config: delete the test plan", "commit_ref": null, "pull_url": null, "state": "accepted", "archived": false, "hash": "c28ca91c317eb418694d1655dd35ff48d01c45a0", "submitter": { "id": 2034, "url": "http://patchwork.dpdk.org/api/people/2034/?format=api", "name": "Yan Xia", "email": "yanx.xia@intel.com" }, "delegate": null, "mbox": "http://patchwork.dpdk.org/project/dts/patch/20211202111453.146572-1-yanx.xia@intel.com/mbox/", "series": [ { "id": 20829, "url": "http://patchwork.dpdk.org/api/series/20829/?format=api", "web_url": "http://patchwork.dpdk.org/project/dts/list/?series=20829", "date": "2021-12-02T11:14:51", "name": "[V3,1/3] test_plans/fortville_rss_granularity_config: delete the test plan", "version": 3, "mbox": "http://patchwork.dpdk.org/series/20829/mbox/" } ], "comments": "http://patchwork.dpdk.org/api/patches/104814/comments/", "check": "pending", "checks": "http://patchwork.dpdk.org/api/patches/104814/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 91A0BA0C47;\n\tThu, 2 Dec 2021 04:14:47 +0100 (CET)", "from [217.70.189.124] (localhost [127.0.0.1])\n\tby mails.dpdk.org (Postfix) with ESMTP id 6C6E84067B;\n\tThu, 2 Dec 2021 04:14:47 +0100 (CET)", "from mga01.intel.com (mga01.intel.com [192.55.52.88])\n by mails.dpdk.org (Postfix) with ESMTP id A822240140\n for <dts@dpdk.org>; Thu, 2 Dec 2021 04:14:45 +0100 (CET)", "from fmsmga006.fm.intel.com ([10.253.24.20])\n by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;\n 01 Dec 2021 19:14:44 -0800", "from unknown (HELO dpdk.lan) ([10.240.183.77])\n by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;\n 01 Dec 2021 19:14:42 -0800" ], "X-IronPort-AV": [ "E=McAfee;i=\"6200,9189,10185\"; a=\"260605761\"", "E=Sophos;i=\"5.87,280,1631602800\"; d=\"scan'208\";a=\"260605761\"", "E=Sophos;i=\"5.87,280,1631602800\"; d=\"scan'208\";a=\"745697915\"" ], "From": "Yan Xia <yanx.xia@intel.com>", "To": "dts@dpdk.org", "Cc": "Yan Xia <yanx.xia@intel.com>", "Subject": "[dts][PATCH V3 1/3] test_plans/fortville_rss_granularity_config:\n delete the test plan", "Date": "Thu, 2 Dec 2021 11:14:51 +0000", "Message-Id": "<20211202111453.146572-1-yanx.xia@intel.com>", "X-Mailer": "git-send-email 2.33.1", "MIME-Version": "1.0", "Content-Transfer-Encoding": "8bit", "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" }, "content": "delete fortville_rss_granularity_config test plan\ndpdk commit id: 81db321da ethdev: remove legacy HASH filter type support\n\nSigned-off-by: Yan Xia <yanx.xia@intel.com>\n---\n ...ville_rss_granularity_config_test_plan.rst | 321 ------------------\n 1 file changed, 321 deletions(-)\n delete mode 100644 test_plans/fortville_rss_granularity_config_test_plan.rst", "diff": "diff --git a/test_plans/fortville_rss_granularity_config_test_plan.rst b/test_plans/fortville_rss_granularity_config_test_plan.rst\ndeleted file mode 100644\nindex 18592b1e..00000000\n--- a/test_plans/fortville_rss_granularity_config_test_plan.rst\n+++ /dev/null\n@@ -1,321 +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-Fortville Granularity Configuration of RSS and 32-bit GRE key Tests\n-===================================================================\n-\n-Description\n-===========\n-\n-This document provides test plan for testing the function of Fortville:\n-\n-1. Support granularity configuration of RSS\n-\n- By default Fortville uses hash input set preloaded from NVM image which\n- includes all fields IPv4/v6+TCP/UDP port. Potential problem for this is\n- global configuration per device and can affect all ports. It is required\n- that hash input set can be configurable, such as using IPv4 only or IPv6\n- only or IPv4/v6+TCP/UDP.\n-\n-2. support 32-bit GRE keys\n-\n- By default Fortville extracts only 24 bits of GRE key to FieldVector (NVGRE\n- use case) but for Telco use cases full 32-bit GRE key is needed. It is\n- required that both 24-bit and 32-bit keys for GRE should be supported. the\n- test plan is to test the API to switch between 24-bit and 32-bit keys\n-\n-\n-Prerequisites\n--------------\n-\n-1. Hardware:\n-\n- * 1x Fortville_eagle NIC (4x 10G)\n- * 1x Fortville_spirit NIC (2x 40G)\n- * 2x Fortville_spirit_single NIC (1x 40G)\n-\n-2. Software:\n-\n- * dpdk: http://dpdk.org/git/dpdk\n- * scapy: http://www.secdev.org/projects/scapy/\n-\n-3. Bind one port to DPDK driver::\n-\n- ./usertools/dpdk-devbind.py -b igb_uio 05:00.0\n-\n- Suppose the MAC address of the port is \"00:00:00:00:01:00\".\n-\n-\n-Test Case 1: test with flow type ipv4-tcp\n-=========================================\n-\n-1. config testpmd on DUT\n-\n- 1. set up testpmd with Fortville NICs::\n-\n- ./testpmd -c 0x1ffff -n 4 -- -i --coremask=0x1fffe --portmask=0x1 --rxq=16 --txq=16 --tx-offloads=0x8fff\n-\n- 2. Reta Configuration(optional, if not set, will use default)::\n-\n- testpmd> port config 0 rss reta (hash_index,queue_id)\n-\n- 3. PMD fwd only receive the packets::\n-\n- testpmd> set fwd rxonly\n-\n- 4. rss received package type configuration::\n-\n- testpmd> port config all rss tcp\n-\n- 5. set hash function::\n-\n- testpmd>set_hash_global_config 0 toeplitz ipv4-tcp enable\n-\n- 6. verbose configuration::\n-\n- testpmd> set verbose 8\n-\n- 7. start packet receive::\n-\n- testpmd> start\n-\n-2. using scapy to send packets with ipv4-tcp on tester::\n-\n- sendp([Ether(dst=\"00:00:00:00:01:00\")/IP(src=\"192.168.0.1\", dst=\"192.168.0.2\")/TCP(sport=1024,dport=1025)], iface=tester_itf)\n-\n- then got hash value and queue value that output from the testpmd on DUT.\n-\n-3. set hash input set to \"none\" by testpmd on dut::\n-\n- testpmd> set_hash_input_set 0 ipv4-tcp none select\n-\n- send packet as step 2, got hash value and queue value that output from the\n- testpmd on DUT, the values should be different from the values in step 2.\n-\n-4. set hash input set by testpmd on dut, enable src-ipv4 & dst-ipv4::\n-\n- testpmd> set_hash_input_set 0 ipv4-tcp src-ipv4 add\n- testpmd> set_hash_input_set 0 ipv4-tcp dst-ipv4 add\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the values should be\n- different from the values in step 2.\n-\n-5. set hash input set by testpmd on dut, enable src-ipv4, dst-ipv4, tcp-src-port, tcp-dst-port::\n-\n- testpmd> set_hash_input_set 0 ipv4-tcp tcp-src-port add\n- testpmd> set_hash_input_set 0 ipv4-tcp tcp-dst-port add\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the values\n- should be different with the values from step 3 & step 4, should be same as step 2.\n-\n-6. set hash input set by testpmd on dut, enable tcp-src-port, tcp-dst-port::\n-\n- testpmd> set_hash_input_set 0 ipv4-tcp none select\n- testpmd> set_hash_input_set 0 ipv4-tcp tcp-src-port add\n- testpmd> set_hash_input_set 0 ipv4-tcp tcp-dst-port add\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the values should be\n- should be different with the values from step2 & step 3 & step 4 & step 5.\n-\n- So it can be approved that with flow type ipv4-tcp, rss hash can be calculated by only included IPv4 fields\n- or only included TCP fields or both IPv4+TCP fields.\n-\n-\n-Test Case 2: test with flow type ipv4-udp\n-=========================================\n-\n-1. config testpmd on DUT\n-\n- 1. set up testpmd with Fortville NICs::\n-\n- ./testpmd -c 0x1ffff -n 4 -- -i --coremask=0x1fffe --portmask=0x1 --rxq=16 --txq=16 --tx-offloads=0x8fff\n-\n- 2. Reta Configuration(optional, if not set, will use default)::\n-\n- testpmd> port config 0 rss reta (hash_index,queue_id)\n-\n- 3. PMD fwd only receive the packets::\n-\n- testpmd> set fwd rxonly\n-\n- 4. rss received package type configuration::\n-\n- testpmd> port config all rss udp\n-\n- 5. set hash function::\n-\n- testpmd>set_hash_global_config 0 toeplitz ipv4-udp enable\n-\n- 6. verbose configuration::\n-\n- testpmd> set verbose 8\n-\n- 7. start packet receive::\n-\n- testpmd> start\n-\n-2. using scapy to send packets with ipv4-udp on tester::\n-\n-\n- sendp([Ether(dst=\"00:00:00:00:01:00\")/IP(src=\"192.168.0.1\", dst=\"192.168.0.2\")/UDP(sport=1024,dport=1025)], iface=tester_itf))\n-\n- then got hash value and queue value that output from the testpmd on DUT.\n-\n-3. set hash input set to \"none\" by testpmd on dut::\n-\n- testpmd> set_hash_input_set 0 ipv4-udp none select\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the values should be\n- different from the values in step 2.\n-\n-4. set hash input set by testpmd on dut, enable src-ipv4 and dst-ipv4::\n-\n- testpmd> set_hash_input_set 0 ipv4-udp src-ipv4 add\n- testpmd> set_hash_input_set 0 ipv4-udp dst-ipv4 add\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the values should be\n- different from the values in step 2 & step 3.\n-\n-5. set hash input set by testpmd on dut, enable src-ipv4, dst-ipv4, udp-src-port, udp-dst-port::\n-\n- testpmd> set_hash_input_set 0 ipv4-udp udp-src-port add\n- testpmd> set_hash_input_set 0 ipv4-udp udp-dst-port add\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the values should be\n- should be different with the values from step 3 & step 4, should be same as step 2.\n-\n-6. set hash input set by testpmd on dut, enable udp-src-port, udp-dst-port::\n-\n- testpmd> set_hash_input_set 0 ipv4-udp none select\n- testpmd> set_hash_input_set 0 ipv4-udp udp-src-port add\n- testpmd> set_hash_input_set 0 ipv4-udp udp-dst-port add\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the values should be\n- should be different with the values from step2 & step 3 & step 4 & step 5.\n-\n- So it can be approved that with flow type ipv4-udp, rss hash can be calculated by only included IPv4 fields\n- or only included UDP fields or both IPv4+UDP fields.\n-\n-Test Case 3: test with flow type ipv6-tcp\n-=========================================\n-\n-test method is same as Test Case 1, but it need change all ipv4 to ipv6,\n-and using scapy to send packets with ipv6-tcp on tester::\n-\n- sendp([Ether(dst=\"00:00:00:00:01:00\")/IPv6(src=\"3ffe:2501:200:1fff::1\", dst=\"3ffe:2501:200:3::2\")/TCP(sport=1024,dport=1025)], iface=tester_itf)\n-\n-and the test result should be same as Test Case 1.\n-\n-\n-Test Case 4: test with flow type ipv6-udp\n-=========================================\n-\n-test method is same as Test Case 2, but it need change all ipv4 to ipv6,\n-and using scapy to send packets with ipv6-udp on tester::\n-\n- sendp([Ether(dst=\"00:00:00:00:01:00\")/IPv6(src=\"3ffe:2501:200:1fff::1\", dst=\"3ffe:2501:200:3::2\")/UDP(sport=1024,dport=1025)], iface=tester_itf)\n-\n-and the test result should be same as Test Case 2.\n-\n-\n-Test Case 6: 32-bit GRE keys and 24-bit GRE keys test\n-=====================================================\n-\n-1. config testpmd on DUT\n-\n- 1. set up testpmd with Fortville NICs::\n-\n- ./testpmd -c 0x1ffff -n 4 -- -i --coremask=0x1fffe --portmask=0x1 --rxq=16 --txq=16 --tx-offloads=0x8fff\n-\n- 2. Reta Configuration(optional, if not set, will use default)::\n-\n- testpmd> port config 0 rss reta (hash_index,queue_id)\n-\n- 3. PMD fwd only receive the packets::\n-\n- testpmd> set fwd rxonly\n-\n- 4. rss received package type configuration::\n-\n- testpmd> port config all rss all\n-\n- 5. set hash function::\n-\n- testpmd>set_hash_global_config 0 toeplitz ipv4-other enable\n-\n- 6. verbose configuration::\n-\n- testpmd> set verbose 8\n-\n- 7. start packet receive::\n-\n- testpmd> start\n-\n-2. using scapy to send packets with GRE header on tester::\n-\n- sendp([Ether(dst=\"00:00:00:00:01:00\")/IP(src=\"192.168.0.1\",dst=\"192.168.0.2\",proto=47)/GRE(key_present=1,proto=2048,key=67108863)/IP()], iface=tester_itf)\n-\n- then got hash value and queue value that output from the testpmd on DUT.\n-\n-3. set hash input set to \"none\" by testpmd on dut::\n-\n- testpmd> set_hash_input_set 0 ipv4-other none select\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the value should be\n- different with the values in step 2.\n-\n-4. set hash input set by testpmd on dut, enable src-ipv4, dst-ipv4::\n-\n- testpmd> set_hash_input_set 0 ipv4-other src-ipv4 add\n- testpmd> set_hash_input_set 0 ipv4-other dst-ipv4 add\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the value should be\n- same with the values in step 2.\n-\n-5. set hash input set and gre-key-len=3 by testpmd on dut, enable gre-key::\n-\n- testpmd> global_config 0 gre-key-len 3\n- testpmd> set_hash_input_set 0 ipv4-other gre-key add\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the values should be\n- different with the values in step 2 & step3.\n-\n-6. set gre-key-len=4 by testpmd on dut, enable gre-key::\n-\n- testpmd> global_config 0 gre-key-len 4\n-\n- send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the values should be\n- different with the values in step 2 & step3 & step 5.\n-\n- So with gre-key-len=3 (24bit gre key) or gre-key-len=4 (32bit gre key), different rss hash value and queue value\n- can be got, it can be proved that 32bit & 24bit gre key are supported by Fortville.\n", "prefixes": [ "V3", "1/3" ] }{ "id": 104814, "url": "