DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Akhil Goyal <gakhil@marvell.com>
Cc: dev@dpdk.org, jerinj@marvell.com, vattunuru@marvell.com,
	techboard@dpdk.org
Subject: Re: [PATCH v4] examples/l2fwd-macsec: add MACsec forwarding application
Date: Thu, 09 Nov 2023 23:28:51 +0100	[thread overview]
Message-ID: <14164652.lVVuGzaMjS@thomas> (raw)
In-Reply-To: <20231109210122.2493856-1-gakhil@marvell.com>

Hi Akhil,

09/11/2023 22:01, Akhil Goyal:
> Added a new application based on l2fwd to demonstrate inline protocol
> offload MACsec performance using rte_security APIs.

In general we try to avoid adding a new example application.
Does this one has been discussed already with the techboard?
We need a good justification for an exception.
Why not merging it in l2fwd-crypto?



  reply	other threads:[~2023-11-09 22:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 13:20 [PATCH] " Akhil Goyal
2023-10-31 18:44 ` [PATCH v2] " Akhil Goyal
2023-11-03  7:32   ` [PATCH v3] " Akhil Goyal
2023-11-09 21:01     ` [PATCH v4] " Akhil Goyal
2023-11-09 22:28       ` Thomas Monjalon [this message]
2023-11-13  5:03         ` [EXT] " Akhil Goyal

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=14164652.lVVuGzaMjS@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=techboard@dpdk.org \
    --cc=vattunuru@marvell.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).