From: Thomas Monjalon <thomas@monjalon.net>
To: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] fib6: improve lookup performance
Date: Wed, 13 Jan 2021 22:02:05 +0100 [thread overview]
Message-ID: <28256657.O8AXx8v4Wm@thomas> (raw)
In-Reply-To: <BYAPR11MB33012C202EFC5936E17DA6579AAA0@BYAPR11MB3301.namprd11.prod.outlook.com>
12/01/2021 15:13, Ananyev, Konstantin:
>
> > Improved performance for AVX512 FIB6 lookup by doubling the number
> > of flows being processed
> >
> > Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied, thanks
PS: added "AVX512" in the title
next prev parent reply other threads:[~2021-01-13 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 18:25 Vladimir Medvedkin
2021-01-12 14:13 ` Ananyev, Konstantin
2021-01-13 21:02 ` Thomas Monjalon [this message]
2021-01-13 11:16 ` Kinsella, Ray
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=28256657.O8AXx8v4Wm@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.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).