From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] ip_pipeline: fix false cacheline sharing among threads
Date: Tue, 14 Jun 2016 21:13:52 +0200 [thread overview]
Message-ID: <2051818.XZUsO1yvAA@xps13> (raw)
In-Reply-To: <1465735367-187704-1-git-send-email-jasvinder.singh@intel.com>
2016-06-12 13:42, Jasvinder Singh:
> In ip_pipeline app, the structure app_thread_data needs to be aligned to
> the cache line boundary as threads on different cpu cores are accessing
> fields of the app->thread_data and having this structure not aligned on
> cacheline boundary leads to false cacheline sharing.
>
> Fixes: 7f64b9c004aa ("examples/ip_pipeline: rework config file syntax")
>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-06-14 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 15:19 [dpdk-dev] [PATCH] " Jasvinder Singh
2016-06-12 12:42 ` [dpdk-dev] [PATCH v2] " Jasvinder Singh
2016-06-14 19: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=2051818.XZUsO1yvAA@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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).