From: Thomas Monjalon <thomas@monjalon.net>
To: Shani Peretz <shperetz@nvidia.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com, Ori Kam <orika@nvidia.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Maayan Kashani <mkashani@nvidia.com>
Subject: Re: [PATCH v3] examples/flow_filtering: introduce use cases snippets
Date: Wed, 20 Nov 2024 02:15:32 +0100 [thread overview]
Message-ID: <1918899.1xdlsreqCQ@thomas> (raw)
In-Reply-To: <20241014094737.1348a918@hermes.local>
14/10/2024 18:47, Stephen Hemminger:
> On Mon, 30 Sep 2024 22:53:21 +0300
> Shani Peretz <shperetz@nvidia.com> wrote:
>
> > These code snippets demonstrate rule creation using
> > template and non-template APIs.
> > They include functions that enable developers to create rules.
> > The purpose of providing these snippets is to allow developers
> > to reuse them, thereby saving time and effort during the
> > implementation of flow rules.
> >
> > The code snippets are categorized based on their usage and can be copied,
> > paste and modified to suit any requirements.
> > The snippets provided here are kept up to date and are being compiled
> > along with the rest of the examples.
> >
> > There is a skeleton that demonstrates rule creation
> > using both template and non template APIs.
> >
> > Developers can change the functions in the skeleton to the corresponding
> > snippet functions with the appropriate suffix and create rules using the
> > snippets themselves for easy testing. Each snippet has the same functions
> > to implement the actions and patterns for the corresponding feature.
> >
> > Signed-off-by: Shani Peretz <shperetz@nvidia.com>
>
> Not sure why the intel-compilation failed but other builds worked.
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Applied, thanks.
prev parent reply other threads:[~2024-11-20 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 13:53 [PATCH] " Shani Peretz
2024-09-30 16:40 ` [PATCH v2] " Shani Peretz
2024-09-30 16:58 ` Stephen Hemminger
2024-09-30 17:53 ` Bruce Richardson
2024-09-30 19:53 ` [PATCH v3] " Shani Peretz
2024-10-14 16:47 ` Stephen Hemminger
2024-11-20 1:15 ` 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=1918899.1xdlsreqCQ@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--cc=shperetz@nvidia.com \
--cc=stephen@networkplumber.org \
/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).