DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, dharmik.thakkar@arm.com,
	nd@arm.com
Subject: Re: [dpdk-dev] [PATCH v2] rcu/test: make gloabl variable per core
Date: Wed, 05 Jun 2019 14:16:17 +0200	[thread overview]
Message-ID: <3355012.7oxlcTFSm5@xps> (raw)
In-Reply-To: <3230523.q5hRvnNJ3y@xps>

05/06/2019 12:50, Thomas Monjalon:
> Bad start, there is a typo in the title :)
> 
> 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.
> 
> > Reported-by: David Marchand <david.marchand@redhat.com>
> > Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> > Reviewed-by: Dharmik Thakkar <dharmik.thakkar@arm.com>
> > Tested-by: David Marchand <david.marchand@redhat.com>

Applied, thanks



  reply	other threads:[~2019-06-05 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 20:42 [dpdk-dev] [PATCH] " Honnappa Nagarahalli
2019-05-15 20:42 ` Honnappa Nagarahalli
2019-05-16  1:14 ` [dpdk-dev] [PATCH v2] " Honnappa Nagarahalli
2019-05-16  1:14   ` Honnappa Nagarahalli
2019-06-05 10:50   ` Thomas Monjalon
2019-06-05 12:16     ` Thomas Monjalon [this message]
2019-06-07  6:30     ` Honnappa Nagarahalli
2019-06-09  8:13       ` 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=3355012.7oxlcTFSm5@xps \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dharmik.thakkar@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --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 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).