From: "Eads, Gage" <gage.eads@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] event/octeontx: fix missing enqueue smp barrier
Date: Tue, 13 Jun 2017 23:06:54 +0000 [thread overview]
Message-ID: <9184057F7FC11744A2107296B6B8EB1E01ED30AA@FMSMSX108.amr.corp.intel.com> (raw)
In-Reply-To: <20170609131603.13483-1-jerin.jacob@caviumnetworks.com>
> -----Original Message-----
> From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com]
> Sent: Friday, June 9, 2017 8:16 AM
> To: dev@dpdk.org
> Cc: hemant.agrawal@nxp.com; Eads, Gage <gage.eads@intel.com>; Van
> Haaren, Harry <harry.van.haaren@intel.com>; Jerin Jacob
> <jerin.jacob@caviumnetworks.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] event/octeontx: fix missing enqueue smp barrier
>
> Typically RTE_EVENT_OP_NEW issued by the producer lcore. To reflect the
> write changes issued by the producer lcore on worker lcore, an SMP write
> barrier is required on producer enqueue. Fixing the missing
> rte_smp_wmb() on enqueue with RTE_EVENT_OP_NEW.
>
> CC: stable@dpdk.org
> Fixes: f10d322eff76 ("event/octeontx: support worker enqueue")
>
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Acked-by: Gage Eads <gage.eads@intel.com>
next prev parent reply other threads:[~2017-06-13 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 13:16 Jerin Jacob
2017-06-13 23:06 ` Eads, Gage [this message]
2017-06-20 14:19 ` 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=9184057F7FC11744A2107296B6B8EB1E01ED30AA@FMSMSX108.amr.corp.intel.com \
--to=gage.eads@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=stable@dpdk.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).