From: Thomas Monjalon <thomas@monjalon.net>
To: Stanislaw Kardach <kda@semihalf.com>
Cc: dev@dpdk.org, Michal Mazurek <maz@semihalf.com>,
Frank Zhao <Frank.Zhao@starfivetech.com>,
Sam Grove <sam.grove@sifive.com>,
upstream@semihalf.com, "Medvedkin,
Vladimir" <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH v4 2/2] lpm: add a scalar version of lookupx4 function
Date: Fri, 03 Jun 2022 11:23:39 +0200 [thread overview]
Message-ID: <1791626.atdPhlSkOF@thomas> (raw)
In-Reply-To: <f9aa53c9-9f01-8da0-2888-91f6cf1b0b53@intel.com>
01/06/2022 13:52, Medvedkin, Vladimir:
> On 01/06/2022 12:15, Stanislaw Kardach wrote:
> > From: Michal Mazurek <maz@semihalf.com>
> >
> > Add an implementation of the rte_lpm_lookupx4() function for platforms
> > without support for vector operations.
> >
> > This will be useful in the upcoming RISC-V port as well as any platform
> > which may want to start with a basic level of LPM support.
> >
> > Signed-off-by: Michal Mazurek <maz@semihalf.com>
> > Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
>
> Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Series applied, thanks.
next prev parent reply other threads:[~2022-06-03 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 11:15 [PATCH v4 1/2] lpm: add const to lpm arg of rte_lpm_lookup Stanislaw Kardach
2022-06-01 11:15 ` [PATCH v4 2/2] lpm: add a scalar version of lookupx4 function Stanislaw Kardach
2022-06-01 11:52 ` Medvedkin, Vladimir
2022-06-03 9:23 ` Thomas Monjalon [this message]
2022-06-02 20:52 ` [PATCH v4 1/2] lpm: add const to lpm arg of rte_lpm_lookup Thomas Monjalon
2022-06-03 7:29 ` Bruce Richardson
2022-06-03 7: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=1791626.atdPhlSkOF@thomas \
--to=thomas@monjalon.net \
--cc=Frank.Zhao@starfivetech.com \
--cc=dev@dpdk.org \
--cc=kda@semihalf.com \
--cc=maz@semihalf.com \
--cc=sam.grove@sifive.com \
--cc=upstream@semihalf.com \
--cc=vladimir.medvedkin@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).