All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Xiaoyun Li <xiaoyun.li@intel.com>
Cc: ferruh.yigit@intel.com, dev@dpdk.org, arybchenko@solarflare.com,
	david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH v2] examples/tep_term: deprecate this example
Date: Tue, 20 Oct 2020 13:42:44 +0200	[thread overview]
Message-ID: <4090967.IOY7mMoEkq@thomas> (raw)
In-Reply-To: <20201020061125.38367-1-xiaoyun.li@intel.com>

20/10/2020 08: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.
> ---
>  MAINTAINERS                                   |    4 -
>  .../img/tep_termination_arch.svg              | 1400 -----------------
>  doc/guides/sample_app_ug/index.rst            |    1 -
>  doc/guides/sample_app_ug/tep_termination.rst  |  233 ---
>  doc/guides/testpmd_app_ug/testpmd_funcs.rst   |   43 +
>  examples/meson.build                          |    2 +-
>  examples/tep_termination/Makefile             |   45 -
>  examples/tep_termination/main.c               | 1235 ---------------
>  examples/tep_termination/main.h               |   93 --
>  examples/tep_termination/meson.build          |   16 -
>  examples/tep_termination/vxlan.c              |  243 ---
>  examples/tep_termination/vxlan.h              |   57 -
>  examples/tep_termination/vxlan_setup.c        |  443 ------
>  examples/tep_termination/vxlan_setup.h        |   58 -
>  14 files changed, 44 insertions(+), 3829 deletions(-)

Please list this example as a removed item in the release notes.
Thanks




  parent reply	other threads:[~2020-10-20 11:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  8:27 [dpdk-dev] [PATCH] examples/tep_term: deprecate this example 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 [this message]
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

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=4090967.IOY7mMoEkq@thomas \
    --to=thomas@monjalon.net \
    --cc=arybchenko@solarflare.com \
    --cc=david.marchand@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.