List comments

GET /api/covers/41340/comments/
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

[
    {
        "id": 82516,
        "web_url": "http://patches.dpdk.org/comment/82516/",
        "msgid": "<1abcbded-425c-c137-af00-7d8f17805cb9@intel.com>",
        "date": "2018-06-22T07:42:10",
        "subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
        "submitter": {
            "id": 482,
            "url": "http://patches.dpdk.org/api/people/482/",
            "name": "Mohammad Abdul Awal",
            "email": "mohammad.abdul.awal@intel.com"
        },
        "content": "Hi Nelio,\n\n\nOn 21/06/2018 08:13, Nelio Laranjeiro wrote:\n> This series adds an easy and maintainable configuration version support for\n> those two actions for 18.08 by using global variables in testpmd to store the\n> necessary information for the tunnel encapsulation.  Those variables are used\n> in conjunction of RTE_FLOW_ACTION_{VXLAN,NVGRE}_ENCAP action to create easily\n> the action for flows.\n>\n> A common way to use it:\n>\n>   set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>   flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n\nThis way we can define only one tunnel for all the flows. This is not a \nconvenient for testing a scenario (e.g. mutiport or switch) with \nmultiple tunnels. Isn't it?\n\nRegards,\nAwal.",
        "headers": {
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "X-Original-To": "patchwork@dpdk.org",
            "Date": "Fri, 22 Jun 2018 08:42:10 +0100",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "In-Reply-To": "<cover.1529420040.git.nelio.laranjeiro@6wind.com>",
            "Message-ID": "<1abcbded-425c-c137-af00-7d8f17805cb9@intel.com>",
            "X-BeenThere": "dev@dpdk.org",
            "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>",
            "References": "<cover.1529332365.git.nelio.laranjeiro@6wind.com>\n\t<cover.1529420040.git.nelio.laranjeiro@6wind.com>",
            "Content-Type": "text/plain; charset=utf-8; format=flowed",
            "To": "Nelio Laranjeiro <nelio.laranjeiro@6wind.com>, dev@dpdk.org,\n\tAdrien Mazarguil <adrien.mazarguil@6wind.com>,\n\tWenzhuo Lu <wenzhuo.lu@intel.com>, Jingjing Wu <jingjing.wu@intel.com>,\n\tBernard Iremonger <bernard.iremonger@intel.com>, Ori Kam\n\t<orika@mellanox.com>, Stephen Hemminger <stephen@networkplumber.org>",
            "User-Agent": "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101\n\tThunderbird/52.8.0",
            "X-Amp-Result": "SKIPPED(no attachment in message)",
            "Errors-To": "dev-bounces@dpdk.org",
            "MIME-Version": "1.0",
            "Received": [
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 1D94A1BABD;\n\tFri, 22 Jun 2018 09:42:22 +0200 (CEST)",
                "from mga12.intel.com (mga12.intel.com [192.55.52.136])\n\tby dpdk.org (Postfix) with ESMTP id 478DC1BA96\n\tfor <dev@dpdk.org>; Fri, 22 Jun 2018 09:42:19 +0200 (CEST)",
                "from fmsmga004.fm.intel.com ([10.253.24.48])\n\tby fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t22 Jun 2018 00:42:19 -0700",
                "from grossi-mobl.ger.corp.intel.com (HELO [10.252.9.106])\n\t([10.252.9.106])\n\tby fmsmga004.fm.intel.com with ESMTP; 22 Jun 2018 00:42:10 -0700"
            ],
            "From": "Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>",
            "Precedence": "list",
            "X-ExtLoop1": "1",
            "X-Amp-File-Uploaded": "False",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "Content-Transfer-Encoding": "7bit",
            "Subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "Content-Language": "en-US",
            "Return-Path": "<dev-bounces@dpdk.org>",
            "X-Mailman-Version": "2.1.15",
            "Delivered-To": "patchwork@dpdk.org",
            "List-Post": "<mailto:dev@dpdk.org>",
            "X-IronPort-AV": "E=Sophos;i=\"5.51,255,1526367600\"; d=\"scan'208\";a=\"65375231\""
        }
    },
    {
        "id": 82518,
        "web_url": "http://patches.dpdk.org/comment/82518/",
        "msgid": "<20180622083158.2teseqebd5qnmvoj@laranjeiro-vm.dev.6wind.com>",
        "date": "2018-06-22T08:31:58",
        "subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
        "submitter": {
            "id": 243,
            "url": "http://patches.dpdk.org/api/people/243/",
            "name": "Nélio Laranjeiro",
            "email": "nelio.laranjeiro@6wind.com"
        },
        "content": "On Fri, Jun 22, 2018 at 08:42:10AM +0100, Mohammad Abdul Awal wrote:\n> Hi Nelio,\n> \n> \n> On 21/06/2018 08:13, Nelio Laranjeiro wrote:\n> > This series adds an easy and maintainable configuration version support for\n> > those two actions for 18.08 by using global variables in testpmd to store the\n> > necessary information for the tunnel encapsulation.  Those variables are used\n> > in conjunction of RTE_FLOW_ACTION_{VXLAN,NVGRE}_ENCAP action to create easily\n> > the action for flows.\n> > \n> > A common way to use it:\n> > \n> >   set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n> >   flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n> \n> This way we can define only one tunnel for all the flows. This is not a\n> convenient for testing a scenario (e.g. mutiport or switch) with multiple\n> tunnels. Isn't it?\n\nHi Awal.\n\nThe \"set vxlan\" command will just configure the outer VXLAN tunnel to be\nused, when the \"flow\" command is invoked, it will use the VXLAN tunnel\ninformation and create a valid VXLAN_ENCAP action.  For instance:\n\n testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n testpmd> set vxlan ipv6 4 34 42 ::1 ::2222 80:12:13:14:15:16 22:22:22:22:22:22\n testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n\nwill create two VLXAN_ENCAP flow one with IPv4 tunnel the second one\nwith an IPv6.  Whereas:\n\n testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n testpmd> flow create 0 ingress pattern eth / ipv4 src is 10.2.3.4 / end\n \tactions vxlan_encap / queue index 0 / end\n testpmd> flow create 0 ingress pattern eth / ipv4 src is 20.2.3.4 / end\n \tactions vxlan_encap / queue index 0 / end\n\nwill encapsulate the packets having as IPv4 source IP 10.2.3.4 and\n20.2.3.4 with the same VXLAN tunnel headers.\n\nRegards,",
        "headers": {
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>",
            "Cc": "dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,\n\tWenzhuo Lu <wenzhuo.lu@intel.com>, Jingjing Wu <jingjing.wu@intel.com>,\n\tBernard Iremonger <bernard.iremonger@intel.com>,\n\tOri Kam <orika@mellanox.com>,\n\tStephen Hemminger <stephen@networkplumber.org>",
            "X-Original-To": "patchwork@dpdk.org",
            "X-Google-DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:references\n\t:mime-version:content-disposition:content-transfer-encoding\n\t:in-reply-to:user-agent;\n\tbh=7vCZukwhpfBJ7L0fPLh6YJouvPaTMNbiVFghP3iEIeE=;\n\tb=ZNrxRpdGUkJlZFfcAER9GHaracMAPIeFptzWWZlU0VpZbqlEIJmBD11FwdDnmjpbGm\n\tsGyHaOmbfqSZm2siSvjBqCmI1GT8E1iTHBTCxiXI21lSNvTP1fs6tWC6+p8aa3rW4BHl\n\tFwKBi8FqiUmd7htP2IANlYjZZuYvwMxBHZU9cnctD7IP0WHKeYGMfAtGeO9BoRD42Zs/\n\t+cJdQHrH5uYs1yMneWwoYVlVWWTkP80oGrm5cx8eaYhIie5IrpBCyEEc6eHGvglVwBJ+\n\tRr7wmWdeFck9XGuiCVzVuAw/Wl4aPbI2Tqdx/c/U5gVEp6YgOPlpcO4621ZUkhJZPNI/\n\tDuLg==",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "In-Reply-To": "<1abcbded-425c-c137-af00-7d8f17805cb9@intel.com>",
            "Message-ID": "<20180622083158.2teseqebd5qnmvoj@laranjeiro-vm.dev.6wind.com>",
            "X-BeenThere": "dev@dpdk.org",
            "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=6wind-com.20150623.gappssmtp.com; s=20150623;\n\th=date:from:to:cc:subject:message-id:references:mime-version\n\t:content-disposition:content-transfer-encoding:in-reply-to\n\t:user-agent; bh=7vCZukwhpfBJ7L0fPLh6YJouvPaTMNbiVFghP3iEIeE=;\n\tb=qM0aB7lDpb+zWwSG8cWV3HCuCBhe/oUGuvBmzSHJXPVnsT2DfY6Y3DDx/36vwhbUvx\n\txM3B7oxKMiXeZ/LDJ40ND1dzjvZJacliVs6Lbah+QSWIhGP0ClVRTeJh7mQEYziiXw+/\n\twO0WJ3eE4DDmPlcz+EbBx3eyVhf6zYwEvQbBV3X0L5CY2ztdPlnqq5u+SklS89u9sPCd\n\tu20sBL8Jeo56xnuUUE5LzD6sfvRoSMHyfJ6DiR81tsFPV8+6dBlSF+WGkwU1dDsgZ4u6\n\t/ClCrYD3QOkc/Ya+1kthxHCfDdVkAiPZ31vM4EX9u3/PL1zvPIB07eMoYQ3ygQs8rLQf\n\twQ3w==",
            "References": "<cover.1529332365.git.nelio.laranjeiro@6wind.com>\n\t<cover.1529420040.git.nelio.laranjeiro@6wind.com>\n\t<1abcbded-425c-c137-af00-7d8f17805cb9@intel.com>",
            "Content-Disposition": "inline",
            "X-Gm-Message-State": "APt69E3ESXcwYBdaSsb85HyP4P759dzwQNcYrQleLchrosdlFl0EsONH\n\tZzrzRSWPXQgOzgqipE/I4N4u",
            "Content-Type": "text/plain; charset=iso-8859-1",
            "To": "Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>",
            "User-Agent": "NeoMutt/20170113 (1.7.2)",
            "Errors-To": "dev-bounces@dpdk.org",
            "X-Google-Smtp-Source": "AAOMgpfD6D4WjSYCorqjq1D3De53wDTM3DitBM15+RG2WYERfZToZk2qi5hsLGMZ4wNHKHt9q51o6g==",
            "MIME-Version": "1.0",
            "Received": [
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id B04D41BB27;\n\tFri, 22 Jun 2018 10:31:44 +0200 (CEST)",
                "from mail-wr0-f193.google.com (mail-wr0-f193.google.com\n\t[209.85.128.193]) by dpdk.org (Postfix) with ESMTP id C3BC71BB20\n\tfor <dev@dpdk.org>; Fri, 22 Jun 2018 10:31:43 +0200 (CEST)",
                "by mail-wr0-f193.google.com with SMTP id e18-v6so5817993wrs.5\n\tfor <dev@dpdk.org>; Fri, 22 Jun 2018 01:31:43 -0700 (PDT)",
                "from laranjeiro-vm.dev.6wind.com\n\t(host.78.145.23.62.rev.coltfrance.com. [62.23.145.78])\n\tby smtp.gmail.com with ESMTPSA id\n\ts13-v6sm7301580wrq.48.2018.06.22.01.31.42\n\t(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);\n\tFri, 22 Jun 2018 01:31:42 -0700 (PDT)"
            ],
            "From": "=?iso-8859-1?q?N=E9lio?= Laranjeiro <nelio.laranjeiro@6wind.com>",
            "Precedence": "list",
            "List-Post": "<mailto:dev@dpdk.org>",
            "Date": "Fri, 22 Jun 2018 10:31:58 +0200",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "Content-Transfer-Encoding": "8bit",
            "Subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>",
            "Return-Path": "<dev-bounces@dpdk.org>",
            "Delivered-To": "patchwork@dpdk.org",
            "X-Received": "by 2002:adf:fac6:: with SMTP id\n\ta6-v6mr710975wrs.74.1529656303444; \n\tFri, 22 Jun 2018 01:31:43 -0700 (PDT)",
            "X-Mailman-Version": "2.1.15"
        }
    },
    {
        "id": 82519,
        "web_url": "http://patches.dpdk.org/comment/82519/",
        "msgid": "<833f6445-bcc2-ae2e-1dc7-45f33e0d8e8e@intel.com>",
        "date": "2018-06-22T08:51:15",
        "subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
        "submitter": {
            "id": 482,
            "url": "http://patches.dpdk.org/api/people/482/",
            "name": "Mohammad Abdul Awal",
            "email": "mohammad.abdul.awal@intel.com"
        },
        "content": "On 22/06/2018 09:31, Nélio Laranjeiro wrote:\n> On Fri, Jun 22, 2018 at 08:42:10AM +0100, Mohammad Abdul Awal wrote:\n>> Hi Nelio,\n>>\n>>\n>> On 21/06/2018 08:13, Nelio Laranjeiro wrote:\n>>> This series adds an easy and maintainable configuration version support for\n>>> those two actions for 18.08 by using global variables in testpmd to store the\n>>> necessary information for the tunnel encapsulation.  Those variables are used\n>>> in conjunction of RTE_FLOW_ACTION_{VXLAN,NVGRE}_ENCAP action to create easily\n>>> the action for flows.\n>>>\n>>> A common way to use it:\n>>>\n>>>    set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>>>    flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n>> This way we can define only one tunnel for all the flows. This is not a\n>> convenient for testing a scenario (e.g. mutiport or switch) with multiple\n>> tunnels. Isn't it?\n> Hi Awal.\n>\n> The \"set vxlan\" command will just configure the outer VXLAN tunnel to be\n> used, when the \"flow\" command is invoked, it will use the VXLAN tunnel\n> information and create a valid VXLAN_ENCAP action.  For instance:\n>\n>   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>   testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n>   testpmd> set vxlan ipv6 4 34 42 ::1 ::2222 80:12:13:14:15:16 22:22:22:22:22:22\n>   testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n>\n> will create two VLXAN_ENCAP flow one with IPv4 tunnel the second one\n> with an IPv6.  Whereas:\n>\n>   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>   testpmd> flow create 0 ingress pattern eth / ipv4 src is 10.2.3.4 / end\n>   \tactions vxlan_encap / queue index 0 / end\n>   testpmd> flow create 0 ingress pattern eth / ipv4 src is 20.2.3.4 / end\n>   \tactions vxlan_encap / queue index 0 / end\n>\n> will encapsulate the packets having as IPv4 source IP 10.2.3.4 and\n> 20.2.3.4 with the same VXLAN tunnel headers.\n\nI understand that the same IPv4 tunnel will be used for both flows in \nyour example above.  I have the following questions.\n\n1) How can we create two or more IPv4 (or IPv6) tunnel?\n1) How can we make the flows to use different IPv4 tunnels?\nAs an example,\n\n  testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n  testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 33:33:33:33:33:33 44:44:44:44:44:44\n  testpmd> flow create 0 ingress pattern end actions vxlan_encap <first tunnel?> / queue index 0 / end\n  testpmd> flow create 0 ingress pattern end actions vxlan_encap <second tunnel?> / queue index 0 / end\n  \n\nIs it possible?\n\nRegards,\nAwal.\n\n>\n> Regards,\n>",
        "headers": {
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>",
            "Cc": "dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,\n\tWenzhuo Lu <wenzhuo.lu@intel.com>, Jingjing Wu <jingjing.wu@intel.com>,\n\tBernard Iremonger <bernard.iremonger@intel.com>, Ori Kam\n\t<orika@mellanox.com>, Stephen Hemminger <stephen@networkplumber.org>",
            "X-Original-To": "patchwork@dpdk.org",
            "Date": "Fri, 22 Jun 2018 09:51:15 +0100",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "In-Reply-To": "<20180622083158.2teseqebd5qnmvoj@laranjeiro-vm.dev.6wind.com>",
            "Message-ID": "<833f6445-bcc2-ae2e-1dc7-45f33e0d8e8e@intel.com>",
            "X-BeenThere": "dev@dpdk.org",
            "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>",
            "References": "<cover.1529332365.git.nelio.laranjeiro@6wind.com>\n\t<cover.1529420040.git.nelio.laranjeiro@6wind.com>\n\t<1abcbded-425c-c137-af00-7d8f17805cb9@intel.com>\n\t<20180622083158.2teseqebd5qnmvoj@laranjeiro-vm.dev.6wind.com>",
            "Content-Type": "text/plain; charset=utf-8; format=flowed",
            "To": "=?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>",
            "User-Agent": "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101\n\tThunderbird/52.8.0",
            "X-Amp-Result": "SKIPPED(no attachment in message)",
            "Errors-To": "dev-bounces@dpdk.org",
            "MIME-Version": "1.0",
            "Received": [
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 5E9B51BB27;\n\tFri, 22 Jun 2018 10:51:25 +0200 (CEST)",
                "from mga11.intel.com (mga11.intel.com [192.55.52.93])\n\tby dpdk.org (Postfix) with ESMTP id 1DE861BA8E\n\tfor <dev@dpdk.org>; Fri, 22 Jun 2018 10:51:22 +0200 (CEST)",
                "from fmsmga004.fm.intel.com ([10.253.24.48])\n\tby fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t22 Jun 2018 01:51:21 -0700",
                "from awalabdu-mobl.ger.corp.intel.com (HELO [10.252.9.106])\n\t([10.252.9.106])\n\tby fmsmga004.fm.intel.com with ESMTP; 22 Jun 2018 01:51:16 -0700"
            ],
            "From": "Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>",
            "Precedence": "list",
            "X-ExtLoop1": "1",
            "X-Amp-File-Uploaded": "False",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "Content-Transfer-Encoding": "8bit",
            "Subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "Content-Language": "en-US",
            "Return-Path": "<dev-bounces@dpdk.org>",
            "X-Mailman-Version": "2.1.15",
            "Delivered-To": "patchwork@dpdk.org",
            "List-Post": "<mailto:dev@dpdk.org>",
            "X-IronPort-AV": "E=Sophos;i=\"5.51,256,1526367600\"; d=\"scan'208\";a=\"65389412\""
        }
    },
    {
        "id": 82520,
        "web_url": "http://patches.dpdk.org/comment/82520/",
        "msgid": "<20180622090859.ewqrwyyvtjj463or@laranjeiro-vm.dev.6wind.com>",
        "date": "2018-06-22T09:08:59",
        "subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
        "submitter": {
            "id": 243,
            "url": "http://patches.dpdk.org/api/people/243/",
            "name": "Nélio Laranjeiro",
            "email": "nelio.laranjeiro@6wind.com"
        },
        "content": "On Fri, Jun 22, 2018 at 09:51:15AM +0100, Mohammad Abdul Awal wrote:\n> \n> \n> On 22/06/2018 09:31, Nélio Laranjeiro wrote:\n> > On Fri, Jun 22, 2018 at 08:42:10AM +0100, Mohammad Abdul Awal wrote:\n> > > Hi Nelio,\n> > > \n> > > \n> > > On 21/06/2018 08:13, Nelio Laranjeiro wrote:\n> > > > This series adds an easy and maintainable configuration version support for\n> > > > those two actions for 18.08 by using global variables in testpmd to store the\n> > > > necessary information for the tunnel encapsulation.  Those variables are used\n> > > > in conjunction of RTE_FLOW_ACTION_{VXLAN,NVGRE}_ENCAP action to create easily\n> > > > the action for flows.\n> > > > \n> > > > A common way to use it:\n> > > > \n> > > >    set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n> > > >    flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n> > > This way we can define only one tunnel for all the flows. This is not a\n> > > convenient for testing a scenario (e.g. mutiport or switch) with multiple\n> > > tunnels. Isn't it?\n> > Hi Awal.\n> > \n> > The \"set vxlan\" command will just configure the outer VXLAN tunnel to be\n> > used, when the \"flow\" command is invoked, it will use the VXLAN tunnel\n> > information and create a valid VXLAN_ENCAP action.  For instance:\n> > \n> >   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n> >   testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n> >   testpmd> set vxlan ipv6 4 34 42 ::1 ::2222 80:12:13:14:15:16 22:22:22:22:22:22\n> >   testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n> > \n> > will create two VLXAN_ENCAP flow one with IPv4 tunnel the second one\n> > with an IPv6.  Whereas:\n> > \n> >   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n> >   testpmd> flow create 0 ingress pattern eth / ipv4 src is 10.2.3.4 / end\n> >   \tactions vxlan_encap / queue index 0 / end\n> >   testpmd> flow create 0 ingress pattern eth / ipv4 src is 20.2.3.4 / end\n> >   \tactions vxlan_encap / queue index 0 / end\n> > \n> > will encapsulate the packets having as IPv4 source IP 10.2.3.4 and\n> > 20.2.3.4 with the same VXLAN tunnel headers.\n> \n> I understand that the same IPv4 tunnel will be used for both flows in your\n> example above.  I have the following questions.\n> \n> 1) How can we create two or more IPv4 (or IPv6) tunnel?\n> 1) How can we make the flows to use different IPv4 tunnels?\n> As an example,\n> \n>  testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>  testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 33:33:33:33:33:33 44:44:44:44:44:44\n>  testpmd> flow create 0 ingress pattern end actions vxlan_encap <first tunnel?> / queue index 0 / end\n>  testpmd> flow create 0 ingress pattern end actions vxlan_encap <second tunnel?> / queue index 0 / end\n> \n\nDoing this, the flows will use the same tunnel, you must do:\n\n testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n testpmd> flow create 0 ingress pattern end actions vxlan_encap <first tunnel?> / queue index 0 / end\n testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 33:33:33:33:33:33 44:44:44:44:44:44\n testpmd> flow create 0 ingress pattern end actions vxlan_encap <second tunnel?> / queue index 0 / end\n\nto have what you want.\n\n> Is it possible?\n\nRegards,",
        "headers": {
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>",
            "Cc": "dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,\n\tWenzhuo Lu <wenzhuo.lu@intel.com>, Jingjing Wu <jingjing.wu@intel.com>,\n\tBernard Iremonger <bernard.iremonger@intel.com>,\n\tOri Kam <orika@mellanox.com>,\n\tStephen Hemminger <stephen@networkplumber.org>",
            "X-Original-To": "patchwork@dpdk.org",
            "X-Google-DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:references\n\t:mime-version:content-disposition:content-transfer-encoding\n\t:in-reply-to:user-agent;\n\tbh=rrePr+VZirfI01USNFoXrDPzgo7TEJC64kGxyd5GlLg=;\n\tb=A79CJmLD99UzHdBBUuu2sB78HjrF/o/Fes/MFUizg1VgorhyYoSQSQy4btmxK1Xime\n\trtlQ3+Gv0jUoJV2dCfVeK+VjHe/1B1UC60sO/dCHM8KnPay3loj5UzCMuuczbyqisyJs\n\tMwD/GTNQ0cQEazXhpynQIjNI2LFYFvXfEl33qLLEM3T/l1cSk/KkWrEymsFvsdvKnkcc\n\tsuKCiMoJq/58E1x7kJ9T8Ufbu61lZAuzG73mKRhB+UBN5R2tGiOYBUTw/J9ZuQXO/MKM\n\tvqrtHy6afMsraxkNfbzXe1HiMPydZgUT/a7+i4EULxBwDrPum8tsIkIOaeTiLAqYuors\n\tKWNg==",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "In-Reply-To": "<833f6445-bcc2-ae2e-1dc7-45f33e0d8e8e@intel.com>",
            "Message-ID": "<20180622090859.ewqrwyyvtjj463or@laranjeiro-vm.dev.6wind.com>",
            "X-BeenThere": "dev@dpdk.org",
            "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=6wind-com.20150623.gappssmtp.com; s=20150623;\n\th=date:from:to:cc:subject:message-id:references:mime-version\n\t:content-disposition:content-transfer-encoding:in-reply-to\n\t:user-agent; bh=rrePr+VZirfI01USNFoXrDPzgo7TEJC64kGxyd5GlLg=;\n\tb=HwsMJQlWAOKbUeBZcAbms7jcCXPiB8CV6qcWdCx/wOzJhimRAPb41HIVtzn/UpdVoz\n\ta/NbseVGT4n3GFLesukB5PuD+IM/o35JJlzAnldSQcH7WeVmTBc1faLSIrWZaV1pmjYL\n\tiPJcFYskFYPrRxScDDNAprNE24fT2GSWWUC61KtQ7/JIFlIgDPWVghUEUlmOUh57Xx/o\n\tKxIugAeZKwnyPLgMxvJXTFK4ueQU9iY3302HwLv92h+bW7ZY3vULR2T3bdsKkeSbnvru\n\t63jYAMjqvNxWQ4Oy755DrQ+v7j3/5C4Cfvc2n3qZHPwxiW1AvW6rOnQs3Ql70+Qwyi1n\n\tKn8w==",
            "References": "<cover.1529332365.git.nelio.laranjeiro@6wind.com>\n\t<cover.1529420040.git.nelio.laranjeiro@6wind.com>\n\t<1abcbded-425c-c137-af00-7d8f17805cb9@intel.com>\n\t<20180622083158.2teseqebd5qnmvoj@laranjeiro-vm.dev.6wind.com>\n\t<833f6445-bcc2-ae2e-1dc7-45f33e0d8e8e@intel.com>",
            "Content-Disposition": "inline",
            "X-Gm-Message-State": "APt69E3zTjzxFk68UH28x+gL7QoSPm/8+d4e50Byonu/adpuoBTdsEyy\n\tctNKFB37TmPc83d4Hgu8YmP1",
            "Content-Type": "text/plain; charset=iso-8859-1",
            "To": "Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>",
            "User-Agent": "NeoMutt/20170113 (1.7.2)",
            "Errors-To": "dev-bounces@dpdk.org",
            "X-Google-Smtp-Source": "AAOMgpdbIxAqSCo2AxDfPQ8HPb7XjSgbCMBOW8QuhLz2DN5hhtA7u2Q6SPep0lfCSp9R6GfJie87RA==",
            "MIME-Version": "1.0",
            "Received": [
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id F033E1BB2C;\n\tFri, 22 Jun 2018 11:08:45 +0200 (CEST)",
                "from mail-wr0-f196.google.com (mail-wr0-f196.google.com\n\t[209.85.128.196]) by dpdk.org (Postfix) with ESMTP id 923491BB20\n\tfor <dev@dpdk.org>; Fri, 22 Jun 2018 11:08:44 +0200 (CEST)",
                "by mail-wr0-f196.google.com with SMTP id k16-v6so5949207wro.0\n\tfor <dev@dpdk.org>; Fri, 22 Jun 2018 02:08:44 -0700 (PDT)",
                "from laranjeiro-vm.dev.6wind.com\n\t(host.78.145.23.62.rev.coltfrance.com. [62.23.145.78])\n\tby smtp.gmail.com with ESMTPSA id\n\tb16-v6sm11490194wrm.15.2018.06.22.02.08.43\n\t(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);\n\tFri, 22 Jun 2018 02:08:43 -0700 (PDT)"
            ],
            "From": "=?iso-8859-1?q?N=E9lio?= Laranjeiro <nelio.laranjeiro@6wind.com>",
            "Precedence": "list",
            "List-Post": "<mailto:dev@dpdk.org>",
            "Date": "Fri, 22 Jun 2018 11:08:59 +0200",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "Content-Transfer-Encoding": "8bit",
            "Subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>",
            "Return-Path": "<dev-bounces@dpdk.org>",
            "Delivered-To": "patchwork@dpdk.org",
            "X-Received": "by 2002:adf:8e93:: with SMTP id\n\tq19-v6mr868601wrb.79.1529658524269; \n\tFri, 22 Jun 2018 02:08:44 -0700 (PDT)",
            "X-Mailman-Version": "2.1.15"
        }
    },
    {
        "id": 82527,
        "web_url": "http://patches.dpdk.org/comment/82527/",
        "msgid": "<92ca13ed-6025-9186-0cb0-b787af470dec@intel.com>",
        "date": "2018-06-22T10:19:14",
        "subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
        "submitter": {
            "id": 482,
            "url": "http://patches.dpdk.org/api/people/482/",
            "name": "Mohammad Abdul Awal",
            "email": "mohammad.abdul.awal@intel.com"
        },
        "content": "On 22/06/2018 10:08, Nélio Laranjeiro wrote:\n> On Fri, Jun 22, 2018 at 09:51:15AM +0100, Mohammad Abdul Awal wrote:\n>>\n>> On 22/06/2018 09:31, Nélio Laranjeiro wrote:\n>>> On Fri, Jun 22, 2018 at 08:42:10AM +0100, Mohammad Abdul Awal wrote:\n>>>> Hi Nelio,\n>>>>\n>>>>\n>>>> On 21/06/2018 08:13, Nelio Laranjeiro wrote:\n>>>>> This series adds an easy and maintainable configuration version support for\n>>>>> those two actions for 18.08 by using global variables in testpmd to store the\n>>>>> necessary information for the tunnel encapsulation.  Those variables are used\n>>>>> in conjunction of RTE_FLOW_ACTION_{VXLAN,NVGRE}_ENCAP action to create easily\n>>>>> the action for flows.\n>>>>>\n>>>>> A common way to use it:\n>>>>>\n>>>>>     set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>>>>>     flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n>>>> This way we can define only one tunnel for all the flows. This is not a\n>>>> convenient for testing a scenario (e.g. mutiport or switch) with multiple\n>>>> tunnels. Isn't it?\n>>> Hi Awal.\n>>>\n>>> The \"set vxlan\" command will just configure the outer VXLAN tunnel to be\n>>> used, when the \"flow\" command is invoked, it will use the VXLAN tunnel\n>>> information and create a valid VXLAN_ENCAP action.  For instance:\n>>>\n>>>    testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>>>    testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n>>>    testpmd> set vxlan ipv6 4 34 42 ::1 ::2222 80:12:13:14:15:16 22:22:22:22:22:22\n>>>    testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n>>>\n>>> will create two VLXAN_ENCAP flow one with IPv4 tunnel the second one\n>>> with an IPv6.  Whereas:\n>>>\n>>>    testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>>>    testpmd> flow create 0 ingress pattern eth / ipv4 src is 10.2.3.4 / end\n>>>    \tactions vxlan_encap / queue index 0 / end\n>>>    testpmd> flow create 0 ingress pattern eth / ipv4 src is 20.2.3.4 / end\n>>>    \tactions vxlan_encap / queue index 0 / end\n>>>\n>>> will encapsulate the packets having as IPv4 source IP 10.2.3.4 and\n>>> 20.2.3.4 with the same VXLAN tunnel headers.\n>> I understand that the same IPv4 tunnel will be used for both flows in your\n>> example above.  I have the following questions.\n>>\n>> 1) How can we create two or more IPv4 (or IPv6) tunnel?\n>> 1) How can we make the flows to use different IPv4 tunnels?\n>> As an example,\n>>\n>>   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>>   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 33:33:33:33:33:33 44:44:44:44:44:44\n>>   testpmd> flow create 0 ingress pattern end actions vxlan_encap <first tunnel?> / queue index 0 / end\n>>   testpmd> flow create 0 ingress pattern end actions vxlan_encap <second tunnel?> / queue index 0 / end\n>>\n> Doing this, the flows will use the same tunnel, you must do:\n>\n>   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n>   testpmd> flow create 0 ingress pattern end actions vxlan_encap <first tunnel?> / queue index 0 / end\n>   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 33:33:33:33:33:33 44:44:44:44:44:44\n>   testpmd> flow create 0 ingress pattern end actions vxlan_encap <second tunnel?> / queue index 0 / end\n>\n> to have what you want.\nOK, thanks for the clarification. So, since there will be only one \nglobal instance of the tunnel,  for any subsequent \"set vxlan\" \noperations, the tunnel created from the last last operation will be \nused. May be it should be cleared in the description/documentation?\n\n>> Is it possible?\n> Regards,\n>",
        "headers": {
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>",
            "Cc": "dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,\n\tWenzhuo Lu <wenzhuo.lu@intel.com>, Jingjing Wu <jingjing.wu@intel.com>,\n\tBernard Iremonger <bernard.iremonger@intel.com>, Ori Kam\n\t<orika@mellanox.com>, Stephen Hemminger <stephen@networkplumber.org>",
            "X-Original-To": "patchwork@dpdk.org",
            "Date": "Fri, 22 Jun 2018 11:19:14 +0100",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "In-Reply-To": "<20180622090859.ewqrwyyvtjj463or@laranjeiro-vm.dev.6wind.com>",
            "Message-ID": "<92ca13ed-6025-9186-0cb0-b787af470dec@intel.com>",
            "X-BeenThere": "dev@dpdk.org",
            "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>",
            "References": "<cover.1529332365.git.nelio.laranjeiro@6wind.com>\n\t<cover.1529420040.git.nelio.laranjeiro@6wind.com>\n\t<1abcbded-425c-c137-af00-7d8f17805cb9@intel.com>\n\t<20180622083158.2teseqebd5qnmvoj@laranjeiro-vm.dev.6wind.com>\n\t<833f6445-bcc2-ae2e-1dc7-45f33e0d8e8e@intel.com>\n\t<20180622090859.ewqrwyyvtjj463or@laranjeiro-vm.dev.6wind.com>",
            "Content-Type": "text/plain; charset=utf-8; format=flowed",
            "To": "=?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>",
            "User-Agent": "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101\n\tThunderbird/52.8.0",
            "X-Amp-Result": "SKIPPED(no attachment in message)",
            "Errors-To": "dev-bounces@dpdk.org",
            "MIME-Version": "1.0",
            "Received": [
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 202361BA96;\n\tFri, 22 Jun 2018 12:19:20 +0200 (CEST)",
                "from mga17.intel.com (mga17.intel.com [192.55.52.151])\n\tby dpdk.org (Postfix) with ESMTP id 0DB4C1BA92\n\tfor <dev@dpdk.org>; Fri, 22 Jun 2018 12:19:18 +0200 (CEST)",
                "from fmsmga004.fm.intel.com ([10.253.24.48])\n\tby fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t22 Jun 2018 03:19:17 -0700",
                "from awalabdu-mobl.ger.corp.intel.com (HELO [10.252.9.106])\n\t([10.252.9.106])\n\tby fmsmga004.fm.intel.com with ESMTP; 22 Jun 2018 03:19:14 -0700"
            ],
            "From": "Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>",
            "Precedence": "list",
            "X-ExtLoop1": "1",
            "X-Amp-File-Uploaded": "False",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "Content-Transfer-Encoding": "8bit",
            "Subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "Content-Language": "en-US",
            "Return-Path": "<dev-bounces@dpdk.org>",
            "X-Mailman-Version": "2.1.15",
            "Delivered-To": "patchwork@dpdk.org",
            "List-Post": "<mailto:dev@dpdk.org>",
            "X-IronPort-AV": "E=Sophos;i=\"5.51,256,1526367600\"; d=\"scan'208\";a=\"65405917\""
        }
    },
    {
        "id": 82691,
        "web_url": "http://patches.dpdk.org/comment/82691/",
        "msgid": "<20180626151502.pt2x2v4orl33pom2@laranjeiro-vm.dev.6wind.com>",
        "date": "2018-06-26T15:15:02",
        "subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
        "submitter": {
            "id": 243,
            "url": "http://patches.dpdk.org/api/people/243/",
            "name": "Nélio Laranjeiro",
            "email": "nelio.laranjeiro@6wind.com"
        },
        "content": "On Fri, Jun 22, 2018 at 11:19:14AM +0100, Mohammad Abdul Awal wrote:\n> On 22/06/2018 10:08, Nélio Laranjeiro wrote:\n> > On Fri, Jun 22, 2018 at 09:51:15AM +0100, Mohammad Abdul Awal wrote:\n> > > \n> > > On 22/06/2018 09:31, Nélio Laranjeiro wrote:\n> > > > On Fri, Jun 22, 2018 at 08:42:10AM +0100, Mohammad Abdul Awal wrote:\n> > > > > Hi Nelio,\n> > > > > \n> > > > > \n> > > > > On 21/06/2018 08:13, Nelio Laranjeiro wrote:\n> > > > > > This series adds an easy and maintainable configuration version support for\n> > > > > > those two actions for 18.08 by using global variables in testpmd to store the\n> > > > > > necessary information for the tunnel encapsulation.  Those variables are used\n> > > > > > in conjunction of RTE_FLOW_ACTION_{VXLAN,NVGRE}_ENCAP action to create easily\n> > > > > > the action for flows.\n> > > > > > \n> > > > > > A common way to use it:\n> > > > > > \n> > > > > >     set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n> > > > > >     flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n> > > > > This way we can define only one tunnel for all the flows. This is not a\n> > > > > convenient for testing a scenario (e.g. mutiport or switch) with multiple\n> > > > > tunnels. Isn't it?\n> > > > Hi Awal.\n> > > > \n> > > > The \"set vxlan\" command will just configure the outer VXLAN tunnel to be\n> > > > used, when the \"flow\" command is invoked, it will use the VXLAN tunnel\n> > > > information and create a valid VXLAN_ENCAP action.  For instance:\n> > > > \n> > > >    testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n> > > >    testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n> > > >    testpmd> set vxlan ipv6 4 34 42 ::1 ::2222 80:12:13:14:15:16 22:22:22:22:22:22\n> > > >    testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end\n> > > > \n> > > > will create two VLXAN_ENCAP flow one with IPv4 tunnel the second one\n> > > > with an IPv6.  Whereas:\n> > > > \n> > > >    testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n> > > >    testpmd> flow create 0 ingress pattern eth / ipv4 src is 10.2.3.4 / end\n> > > >    \tactions vxlan_encap / queue index 0 / end\n> > > >    testpmd> flow create 0 ingress pattern eth / ipv4 src is 20.2.3.4 / end\n> > > >    \tactions vxlan_encap / queue index 0 / end\n> > > > \n> > > > will encapsulate the packets having as IPv4 source IP 10.2.3.4 and\n> > > > 20.2.3.4 with the same VXLAN tunnel headers.\n> > > I understand that the same IPv4 tunnel will be used for both flows in your\n> > > example above.  I have the following questions.\n> > > \n> > > 1) How can we create two or more IPv4 (or IPv6) tunnel?\n> > > 1) How can we make the flows to use different IPv4 tunnels?\n> > > As an example,\n> > > \n> > >   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n> > >   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 33:33:33:33:33:33 44:44:44:44:44:44\n> > >   testpmd> flow create 0 ingress pattern end actions vxlan_encap <first tunnel?> / queue index 0 / end\n> > >   testpmd> flow create 0 ingress pattern end actions vxlan_encap <second tunnel?> / queue index 0 / end\n> > > \n> > Doing this, the flows will use the same tunnel, you must do:\n> > \n> >   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22\n> >   testpmd> flow create 0 ingress pattern end actions vxlan_encap <first tunnel?> / queue index 0 / end\n> >   testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 33:33:33:33:33:33 44:44:44:44:44:44\n> >   testpmd> flow create 0 ingress pattern end actions vxlan_encap <second tunnel?> / queue index 0 / end\n> > \n> > to have what you want.\n> OK, thanks for the clarification. So, since there will be only one global\n> instance of the tunnel,  for any subsequent \"set vxlan\" operations, the\n> tunnel created from the last last operation will be used. May be it should\n> be cleared in the description/documentation?\n\nWill add it in the v5.\n\n> > > Is it possible?\n> > Regards,\n> > \n> \n\nThanks,",
        "headers": {
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>",
            "Cc": "dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,\n\tWenzhuo Lu <wenzhuo.lu@intel.com>, Jingjing Wu <jingjing.wu@intel.com>,\n\tBernard Iremonger <bernard.iremonger@intel.com>,\n\tOri Kam <orika@mellanox.com>,\n\tStephen Hemminger <stephen@networkplumber.org>",
            "X-Original-To": "patchwork@dpdk.org",
            "X-Google-DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:references\n\t:mime-version:content-disposition:content-transfer-encoding\n\t:in-reply-to:user-agent;\n\tbh=+4VgX+ERtDHR4dwOKONJC9HwxTyBtub165viRVoUhS0=;\n\tb=DK5xZMflC48KwiMbjJJ/nd0LE/Sr0RYHDpDkfVQ/OWT8bskMf1hAMhhWjNpLNhg1PV\n\ttNMQVEMg54xQ6yDrJLB5C3Hg+AanjXLvQ6peKYcLtxFiQcyT+QIjSUruxQCsfPYkbjFv\n\tERHCHGxCHTmH+cFDcgafaYy7diu6/4uGCY9F5OalnO7EGzYbD5SH6/W7XWsl1eKxZKP4\n\tIG5e2gOKV2oyTXtr4K0Ekwmr5NmxIWYZBG7wLkiAoDE1ENZXC7ps1z3WYHGb+3Zrf3H1\n\tAWvUDkl7EGTXbrTF76edqR2N7jLzxTr2ckXdt1LJW6qQqr3egaKl9/eXjhxe78Z91K0a\n\t/GOg==",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "In-Reply-To": "<92ca13ed-6025-9186-0cb0-b787af470dec@intel.com>",
            "Message-ID": "<20180626151502.pt2x2v4orl33pom2@laranjeiro-vm.dev.6wind.com>",
            "X-BeenThere": "dev@dpdk.org",
            "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=6wind-com.20150623.gappssmtp.com; s=20150623;\n\th=date:from:to:cc:subject:message-id:references:mime-version\n\t:content-disposition:content-transfer-encoding:in-reply-to\n\t:user-agent; bh=+4VgX+ERtDHR4dwOKONJC9HwxTyBtub165viRVoUhS0=;\n\tb=IbhD5vFpuuMPbsfblCWg5800yzRNAbOtU+lFbGLq2TgIGwxbv6esqJweYSrvCwywSA\n\tV8TtDx9XZLTOZ2usy8+VJOrWlCvBjK5uyXkjJizOjY8AteR6CEp215+OCj6Mh1pOBk/4\n\tF+ORGNhlB2GrHsI/j6WVgsBsaJ0Y79/BpDk1jupGtGOJcu8a2fJgwkGWuZaYDF5Bw3md\n\tTPwD4oSy4JVvXJNsTBLTf1ESC5EKgr5SSGY1vgzkCUn2h/vjdvfVj8VA3iO0/PlK51yi\n\tNaa9q4MDGI2A67v211jiDAAUwBlG6O2JZCwFmDibXtRAbMRwFqWFp1t8Ol4d+449/oJK\n\tm5yg==",
            "References": "<cover.1529332365.git.nelio.laranjeiro@6wind.com>\n\t<cover.1529420040.git.nelio.laranjeiro@6wind.com>\n\t<1abcbded-425c-c137-af00-7d8f17805cb9@intel.com>\n\t<20180622083158.2teseqebd5qnmvoj@laranjeiro-vm.dev.6wind.com>\n\t<833f6445-bcc2-ae2e-1dc7-45f33e0d8e8e@intel.com>\n\t<20180622090859.ewqrwyyvtjj463or@laranjeiro-vm.dev.6wind.com>\n\t<92ca13ed-6025-9186-0cb0-b787af470dec@intel.com>",
            "Content-Disposition": "inline",
            "X-Gm-Message-State": "APt69E3tqlsOC7MuCw+JGGwXNqLQftqi5DLqcawLIRg+pEUFYHAlkG1W\n\tgqSCkWs/wbWAzbY4Ou9GNqlJ",
            "Content-Type": "text/plain; charset=iso-8859-1",
            "To": "Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>",
            "User-Agent": "NeoMutt/20170113 (1.7.2)",
            "Errors-To": "dev-bounces@dpdk.org",
            "X-Google-Smtp-Source": "AAOMgpcGOEN+oOBpTJqhv5a50aYJpYcTKYlKJknW/pTwM92mfZLB/lbHtKejioAPDGv6ZVbGQ4kStw==",
            "MIME-Version": "1.0",
            "Received": [
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id E3B711B8D0;\n\tTue, 26 Jun 2018 17:14:38 +0200 (CEST)",
                "from mail-wr0-f196.google.com (mail-wr0-f196.google.com\n\t[209.85.128.196]) by dpdk.org (Postfix) with ESMTP id 269D71B8CB\n\tfor <dev@dpdk.org>; Tue, 26 Jun 2018 17:14:38 +0200 (CEST)",
                "by mail-wr0-f196.google.com with SMTP id c13-v6so7700060wrq.2\n\tfor <dev@dpdk.org>; Tue, 26 Jun 2018 08:14:38 -0700 (PDT)",
                "from laranjeiro-vm.dev.6wind.com\n\t(host.78.145.23.62.rev.coltfrance.com. [62.23.145.78])\n\tby smtp.gmail.com with ESMTPSA id\n\tb15-v6sm2504121wri.14.2018.06.26.08.14.36\n\t(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);\n\tTue, 26 Jun 2018 08:14:36 -0700 (PDT)"
            ],
            "From": "=?iso-8859-1?q?N=E9lio?= Laranjeiro <nelio.laranjeiro@6wind.com>",
            "Precedence": "list",
            "List-Post": "<mailto:dev@dpdk.org>",
            "Date": "Tue, 26 Jun 2018 17:15:02 +0200",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "Content-Transfer-Encoding": "8bit",
            "Subject": "Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE\n\tEncap/Decap",
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>",
            "Return-Path": "<dev-bounces@dpdk.org>",
            "Delivered-To": "patchwork@dpdk.org",
            "X-Received": "by 2002:a5d:41c5:: with SMTP id\n\te5-v6mr1845410wrq.25.1530026077821; \n\tTue, 26 Jun 2018 08:14:37 -0700 (PDT)",
            "X-Mailman-Version": "2.1.15"
        }
    }
]