From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
Dharmik Thakkar <Dharmik.Thakkar@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2] rcu/test: make gloabl variable per core
Date: Sun, 09 Jun 2019 17:13:57 +0900 [thread overview]
Message-ID: <1657124.WomqKQn9IR@xps> (raw)
In-Reply-To: <VE1PR08MB514965485E9726E0E3CCD4A598100@VE1PR08MB5149.eurprd08.prod.outlook.com>
07/06/2019 15:30, Honnappa Nagarahalli:
> >
> > Bad start, there is a typo in the title :)
> I guess, my apologies do not have any meaning anymore
>
> >
> > 16/05/2019 03:14, Honnappa Nagarahalli:
> > > Each hash entry has a pointer to one uint32 memory location.
> > > However, all the readers increment the same location causing race
> > > conditions. Allocate memory for each thread so that each thread will
> > > increment its own memory location.
> > >
> > > Fixes: b87089b0bb19 ("test/rcu: add API and functional tests")
> >
> > If you run devtools/check-git-log.sh you will see that Cc stable is required for
> > backport.
> I ran this again, it does not show anything.
> I thought, we are not doing maintenance releases for the quarterly releases.
We may do a maintenance. It is not confirmed yet.
Anyway, we can put it in doubt :)
prev parent reply other threads:[~2019-06-09 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 20:42 [dpdk-dev] [PATCH] rcu/test: make gloabl variable per core Honnappa Nagarahalli
2019-05-16 1:14 ` [dpdk-dev] [PATCH v2] " Honnappa Nagarahalli
2019-06-05 10:50 ` Thomas Monjalon
2019-06-05 12:16 ` Thomas Monjalon
2019-06-07 6:30 ` Honnappa Nagarahalli
2019-06-09 8:13 ` Thomas Monjalon [this message]
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=1657124.WomqKQn9IR@xps \
--to=thomas@monjalon.net \
--cc=Dharmik.Thakkar@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nd@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.