DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Sean Morrissey <sean.morrissey@intel.com>
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>, dev@dpdk.org
Subject: Re: [PATCH v1] examples/l3fwd: merge l3fwd-acl into l3fwd
Date: Tue, 29 Mar 2022 11:28:43 +0100	[thread overview]
Message-ID: <YkLfW/nNSEVvsLLz@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20220325151428.1037085-1-sean.morrissey@intel.com>

On Fri, Mar 25, 2022 at 03:14:28PM +0000, Sean Morrissey wrote:
> l3fwd-acl contains duplicate functions to l3fwd.
> For this reason we merge l3fwd-acl code into l3fwd
> with '--lookup acl' cmdline option to run ACL.
> 
> Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
> ---
>  examples/l3fwd-acl/Makefile       |   51 -
>  examples/l3fwd-acl/main.c         | 2272 -----------------------------
>  examples/l3fwd-acl/meson.build    |   13 -
>  examples/l3fwd/Makefile           |    2 +-
>  examples/l3fwd/l3fwd.h            |   39 +-
>  examples/l3fwd/l3fwd_acl.c        | 1123 ++++++++++++++
>  examples/l3fwd/l3fwd_acl.h        |  120 ++
>  examples/l3fwd/l3fwd_acl_scalar.h |  160 ++
>  examples/l3fwd/l3fwd_route.h      |   16 +
>  examples/l3fwd/main.c             |   97 +-
>  examples/l3fwd/meson.build        |    3 +-
>  examples/meson.build              |    1 -
>  12 files changed, 1545 insertions(+), 2352 deletions(-)
>  delete mode 100644 examples/l3fwd-acl/Makefile
>  delete mode 100644 examples/l3fwd-acl/main.c
>  delete mode 100644 examples/l3fwd-acl/meson.build
>  create mode 100644 examples/l3fwd/l3fwd_acl.c
>  create mode 100644 examples/l3fwd/l3fwd_acl.h
>  create mode 100644 examples/l3fwd/l3fwd_acl_scalar.h
> 

Patch also needs to remove/update the docs for:
https://doc.dpdk.org/guides-21.11/sample_app_ug/l3_forward_access_ctrl.html
https://doc.dpdk.org/guides-21.11/sample_app_ug/l3_forward.html

/Bruce

  reply	other threads:[~2022-03-29 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 15:14 Sean Morrissey
2022-03-29 10:28 ` Bruce Richardson [this message]
2022-03-29 10:33 ` Ananyev, Konstantin
2022-03-30 14:04 ` [PATCH v2] " Sean Morrissey
2022-04-02 13:53   ` Ananyev, Konstantin
2022-04-06 10:29   ` [PATCH v3] " Sean Morrissey
2022-04-06 11:47     ` David Marchand
2022-04-06 12:06     ` [PATCH v4] " Sean Morrissey
2022-04-08 17:26       ` Ananyev, Konstantin
2022-04-08 19:01         ` Morrissey, Sean
2022-04-09 11:58           ` Ananyev, Konstantin
2022-04-11  8:41       ` [PATCH v5] " Sean Morrissey
2022-04-11 11:38         ` Ananyev, Konstantin
2022-04-22  9:57         ` [PATCH v6] " Sean Morrissey
2022-06-08  9:50           ` 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=YkLfW/nNSEVvsLLz@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=sean.morrissey@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).