DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Xiaoyun Li <xiaoyun.li@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, arybchenko@solarflare.com
Subject: Re: [dpdk-dev] [PATCH v4] examples/tep_term: deprecate this example
Date: Thu, 29 Oct 2020 12:43:23 +0100	[thread overview]
Message-ID: <6391459.WJGfY7xlGf@thomas> (raw)
In-Reply-To: <20201026081143.73242-1-xiaoyun.li@intel.com>

26/10/2020 09:11, Xiaoyun Li:
> This example sets up a scenario that VXLAN packets can be received
> by different PF queues based on VNID and each queue is bound to a VM
> with a VNID so that the VM can receive its inner packets.
> 
> Usually, OVS is used to do the software encap/decap for VXLAN packets.
> 
> And the VXLAN packets offloading can be replaced with flow rules in
> testpmd like Chapter "Sample VXLAN flow rules" in Testpmd Application
> User Guide.
> 
> And this example hasn't been used for a long time.
> 
> So deprecate this example.
> 
> Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied, thanks



      reply	other threads:[~2020-10-29 11:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  8:27 [dpdk-dev] [PATCH] " Xiaoyun Li
2020-10-19  8:49 ` Thomas Monjalon
2020-10-19  9:19   ` Andrew Rybchenko
2020-10-19  9:13 ` Ferruh Yigit
2020-10-20  5:19   ` Li, Xiaoyun
2020-10-20  6:11 ` [dpdk-dev] [PATCH v2] " Xiaoyun Li
2020-10-20 11:29   ` Ferruh Yigit
2020-10-20 11:42   ` Thomas Monjalon
2020-10-21  1:44     ` Li, Xiaoyun
2020-10-21  2:10 ` [dpdk-dev] [PATCH v3] " Xiaoyun Li
2020-10-26  8:11 ` [dpdk-dev] [PATCH v4] " Xiaoyun Li
2020-10-29 11:43   ` Thomas Monjalon [this message]

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=6391459.WJGfY7xlGf@thomas \
    --to=thomas@monjalon.net \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=xiaoyun.li@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).