From: Thomas Monjalon <thomas@monjalon.net>
To: Pradeep Satyanarayana <pradeep@us.ibm.com>
Cc: "bruce.richardson@intel.com" <bruce.richardson@intel.com>,
Chao Zhu <chaozhu@linux.vnet.ibm.com>,
Dekel Peled <dekelp@mellanox.com>,
dev@dpdk.org, David Christensen <drc@ibm.com>,
"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
Idan Werpoler <Idanw@mellanox.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"ola.liljedahl@arm.com" <ola.liljedahl@arm.com>,
Olga Shern <olgas@mellanox.com>, Ori Kam <orika@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
David Wilder <wilder@us.ibm.com>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] eal/ppc: remove fix of memory barrier for IBM POWER
Date: Thu, 28 Mar 2019 18:56:50 +0100 [thread overview]
Message-ID: <18284767.dla22OQ03R@xps> (raw)
Message-ID: <20190328175650.a3IS3xssnvi8TJOe186cVJAhkI_ZQBe0owDZPDDih3g@z> (raw)
In-Reply-To: <OF1A453A6E.032941CB-ON882583CB.0061925E-882583CB.00621872@notes.na.collabserv.com>
28/03/2019 18:51, Pradeep Satyanarayana:
> From: Pradeep Satyanarayana/Beaverton/IBM
> > From: Thomas Monjalon <thomas@monjalon.net>
> > > Pradeep, Chao,
> > >
> > > Do we have more news?
> > > We must merge this patch for DPDK 19.05-rc1.
> > >
> > > I understand you want to try improving performance
> > > by using lightweight sync for SMP barrier,
> > > and this change can be done later.
> > > First priority is to fix the bug of the general barrier.
> > > That's why I should push this patch before the end of the week.
>
> > Dekel's patch at:
> >
> > http://mails.dpdk.org/archives/dev/2019-March/126746.html
> >
> > seems to be holding up well with the testing done so far. We have
> > also pulled that patch in to test with DTS. If all hold up well,
> > we should be able to let you know by tomorrow morning (US west coast
> time).
>
> Thomas,
>
> This is to confirm that the internal testing has completed and all the
> tests
> passed. So, yes, we can push that into 19.05-rc1.
>
> We will have another patch out for the smp barriers as well. That is still
> being tested.
>
> We will also need to get these patches into 18.11 and higher releases. We
> will work with others to get that done.
OK, thanks
next prev parent reply other threads:[~2019-03-28 17:56 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 12:58 Dekel Peled
2019-03-18 12:58 ` Dekel Peled
2019-03-19 3:24 ` Chao Zhu
2019-03-19 3:24 ` Chao Zhu
2019-03-19 10:05 ` Dekel Peled
2019-03-19 10:05 ` Dekel Peled
2019-03-19 11:14 ` Thomas Monjalon
2019-03-19 11:14 ` Thomas Monjalon
2019-03-19 19:42 ` Shahaf Shuler
2019-03-19 19:42 ` Shahaf Shuler
2019-03-19 20:45 ` Thomas Monjalon
2019-03-19 20:45 ` Thomas Monjalon
2019-03-20 22:40 ` Pradeep Satyanarayana
2019-03-20 22:40 ` Pradeep Satyanarayana
2019-03-21 8:49 ` Shahaf Shuler
2019-03-21 8:49 ` Shahaf Shuler
2019-03-22 1:40 ` Pradeep Satyanarayana
2019-03-22 1:40 ` Pradeep Satyanarayana
2019-03-22 8:49 ` Thomas Monjalon
2019-03-22 8:49 ` Thomas Monjalon
2019-03-22 15:30 ` Pradeep Satyanarayana
2019-03-22 15:30 ` Pradeep Satyanarayana
2019-03-22 17:51 ` Thomas Monjalon
2019-03-22 17:51 ` Thomas Monjalon
2019-03-22 22:57 ` Pradeep Satyanarayana
2019-03-22 22:57 ` Pradeep Satyanarayana
2019-03-24 6:37 ` Shahaf Shuler
2019-03-24 6:37 ` Shahaf Shuler
2019-03-24 17:37 ` Pradeep Satyanarayana
2019-03-24 17:37 ` Pradeep Satyanarayana
2019-03-26 9:15 ` Dekel Peled
2019-03-26 9:15 ` Dekel Peled
2019-03-27 9:19 ` Thomas Monjalon
2019-03-27 9:19 ` Thomas Monjalon
2019-03-27 23:50 ` Pradeep Satyanarayana
2019-03-27 23:50 ` Pradeep Satyanarayana
[not found] ` <OF456B0ECC.006EF7E7-ON882583CA.00827A75-882583CA.0082F7BE@LocalDomain>
2019-03-28 17:51 ` Pradeep Satyanarayana
2019-03-28 17:51 ` Pradeep Satyanarayana
2019-03-28 17:56 ` Thomas Monjalon [this message]
2019-03-28 17:56 ` Thomas Monjalon
2019-03-28 22:50 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-03-28 22:50 ` 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=18284767.dla22OQ03R@xps \
--to=thomas@monjalon.net \
--cc=Idanw@mellanox.com \
--cc=bruce.richardson@intel.com \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=drc@ibm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=konstantin.ananyev@intel.com \
--cc=ola.liljedahl@arm.com \
--cc=olgas@mellanox.com \
--cc=orika@mellanox.com \
--cc=pradeep@us.ibm.com \
--cc=shahafs@mellanox.com \
--cc=wilder@us.ibm.com \
--cc=yskoh@mellanox.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).