From: Jerin Jacob <jerinjacobk@gmail.com>
To: Timothy McDaniel <timothy.mcdaniel@intel.com>
Cc: dpdk-dev <dev@dpdk.org>,
Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
Gage Eads <gage.eads@intel.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2 0/1] Optimize DLB Dequeue
Date: Thu, 29 Apr 2021 12:50:56 +0530 [thread overview]
Message-ID: <CALBAE1NA-RuSXHjPsmDzdazfK7q_pbnY=TAd7Mjh2J4pwiNhKw@mail.gmail.com> (raw)
In-Reply-To: <1618345839-3515-1-git-send-email-timothy.mcdaniel@intel.com>
On Wed, Apr 14, 2021 at 2:02 AM Timothy McDaniel
<timothy.mcdaniel@intel.com> wrote:
>
> This commit optimizes dequeue performance by using x86 vector
> instructions.
>
> Changes since V1:
> Added devargs interface to disable optimization
>
> Depends-on: patch-16345 ("Add DLB 2.5")
Now that series needs rework. Please rebase this series.
Marking as "Change Requested" for this patch.
>
> Timothy McDaniel (1):
> event/dlb: optimize Dequeue Operations
>
> drivers/event/dlb/dlb2.c | 445 ++++++++++++++++++++++++++++++----
> drivers/event/dlb/dlb2_priv.h | 22 +-
> 2 files changed, 414 insertions(+), 53 deletions(-)
>
> --
> 2.23.0
>
next prev parent reply other threads:[~2021-04-29 7:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 17:02 [dpdk-dev] [PATCH] event/dlb2: Optimize Dequeue Operations Timothy McDaniel
2021-03-21 11:10 ` Jerin Jacob
2021-04-13 20:30 ` [dpdk-dev] [PATCH v2 0/1] Optimize DLB Dequeue Timothy McDaniel
2021-04-13 20:30 ` [dpdk-dev] [PATCH v2 1/1] event/dlb: optimize Dequeue Operations Timothy McDaniel
2021-04-29 7:20 ` Jerin Jacob [this message]
2021-04-29 13:45 ` [dpdk-dev] [PATCH v2 0/1] Optimize DLB Dequeue McDaniel, Timothy
2021-05-01 19:07 ` [dpdk-dev] [PATCH v3 0/1] Optimize DLB2 Dequeue Operations McDaniel, Timothy
2021-05-01 19:07 ` [dpdk-dev] [PATCH v3 1/1] event/dlb2: optimize " McDaniel, Timothy
2021-05-04 8:29 ` Jerin Jacob
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='CALBAE1NA-RuSXHjPsmDzdazfK7q_pbnY=TAd7Mjh2J4pwiNhKw@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=gage.eads@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=jerinj@marvell.com \
--cc=thomas@monjalon.net \
--cc=timothy.mcdaniel@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).