DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, Sachin Saxena <sachin.saxena@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] mk: change TLS model for ARMv8 and DPAA machine
Date: Sun, 10 Jun 2018 16:37:03 +0530	[thread overview]
Message-ID: <20180610110700.GA6990@jerin> (raw)
In-Reply-To: <1528180425-27937-1-git-send-email-hemant.agrawal@nxp.com>

-----Original Message-----
> Date: Tue,  5 Jun 2018 12:03:45 +0530
> From: Hemant Agrawal <hemant.agrawal@nxp.com>
> To: dev@dpdk.org
> CC: Sachin Saxena <sachin.saxena@nxp.com>
> Subject: [dpdk-dev] [PATCH] mk: change TLS model for ARMv8 and DPAA machine
> X-Mailer: git-send-email 2.7.4
> 
> From: Sachin Saxena <sachin.saxena@nxp.com>
> 
> Random corruptions observed on ARM platfoms with using
> the dpdk library in shared mode with VPP software (plugin).
> 
> sing traditional TLS scheme resolved the issue.
> 
> Tested with VPP with DPDK as a plugin.
> 
> Signed-off-by: Sachin Saxena <sachin.saxena@nxp.com>
> ---
>  mk/machine/armv8a/rte.vars.mk | 3 +++
>  mk/machine/dpaa/rte.vars.mk   | 3 +++
>  mk/machine/dpaa2/rte.vars.mk  | 3 +++
>  3 files changed, 9 insertions(+)
> 
> diff --git a/mk/machine/armv8a/rte.vars.mk b/mk/machine/armv8a/rte.vars.mk
> index 8252efb..6897cd6 100644
> --- a/mk/machine/armv8a/rte.vars.mk
> +++ b/mk/machine/armv8a/rte.vars.mk
> @@ -29,3 +29,6 @@
>  # CPU_ASFLAGS =
>  
>  MACHINE_CFLAGS += -march=armv8-a+crc+crypto
> +
> +# To avoid TLS corruption issue.
> +MACHINE_CFLAGS += -mtls-dialect=trad

This issue is not reproducible on Cavium ARMv8 platforms. Just wondering,
Do we need to change default ARMv8 config?

The GNU (descriptor) dialect for TLS is the default has been
since for a while on aarch64.

I think, it will be mostly a glibc issue with your SDK based toolchain.
Are you able to reproduce this issue with Linaro toolchain + standard
OS distribution environments? if so, could you please share more
details.

I am only concerned about, any performance issue with traditional tls
dialect model vs descriptor dialect.

I think, we have two options,
1) If you can identify if it is due a specific glibc version then we
could detect at runtime
2) In a worst case, it can be a conditional compilation option.

/Jerin

  reply	other threads:[~2018-06-10 11:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05  6:33 Hemant Agrawal
2018-06-10 11:07 ` Jerin Jacob [this message]
2018-06-11  4:05   ` Sachin Saxena
2018-06-11  7:45     ` Jerin Jacob
2018-06-14  6:42       ` Sachin Saxena
2018-06-24 12:27         ` Jerin Jacob
2018-07-04  9:54 ` [dpdk-dev] [PATCH v2] mk: change TLS model for " Hemant Agrawal
2018-07-12 11:11   ` 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=20180610110700.GA6990@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=sachin.saxena@nxp.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).