DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Vipin Varghese <vipin.varghese@intel.com>
Cc: dev@dpdk.org, harry.van.haaren@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] event/sw: code refractor to reduce the fetch stall
Date: Mon, 2 Apr 2018 13:36:44 +0530	[thread overview]
Message-ID: <20180402080643.GC7280@jerin> (raw)
In-Reply-To: <1519932900-10571-1-git-send-email-vipin.varghese@intel.com>

-----Original Message-----
> Date: Fri, 2 Mar 2018 01:04:59 +0530
> From: Vipin Varghese <vipin.varghese@intel.com>
> To: dev@dpdk.org, harry.van.haaren@intel.com
> CC: Vipin Varghese <vipin.varghese@intel.com>
> Subject: [dpdk-dev] [PATCH 1/2] event/sw: code refractor to reduce the
>  fetch stall
> X-Mailer: git-send-email 2.7.4
> 
> With rearranging the code to prefetch the contents before
> loop check increases performance from single and multistage
> atomic pipeline.
> 
> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>

Harry,

Can you review this patches(1/1 and 1/2)so that I can include it in RC1 pull
request.

  parent reply	other threads:[~2018-04-02  8:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 19:34 Vipin Varghese
2018-03-01 19:35 ` [dpdk-dev] [PATCH 2/2] event/sw: code refractor for sw_refill_pp_buf Vipin Varghese
2018-04-03 12:50   ` Van Haaren, Harry
2018-04-04 11:51     ` Varghese, Vipin
2018-04-04 12:26       ` Van Haaren, Harry
2018-04-02  8:06 ` Jerin Jacob [this message]
2018-04-03 12:47 ` [dpdk-dev] [PATCH 1/2] event/sw: code refractor to reduce the fetch stall Van Haaren, Harry
2018-04-05 11:24 ` [dpdk-dev] [PATCH v2] " Vipin Varghese
2018-04-05  5:56   ` [dpdk-dev] [PATCH v3] " Vipin Varghese
2018-04-05  8:53     ` Jerin Jacob
2018-04-13 16:19       ` Van Haaren, Harry
2018-04-14  5:28         ` 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=20180402080643.GC7280@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.com \
    --cc=vipin.varghese@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).