From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org, jia.he@hxt-semitech.com
Subject: Re: [dpdk-dev] [PATCH] config/thunderx: disable c11 mem model ring implementation
Date: Mon, 29 Jan 2018 16:14:50 +0100 [thread overview]
Message-ID: <1749775.YaGPC7JKFg@xps> (raw)
In-Reply-To: <20171203123730.26782-1-jerin.jacob@caviumnetworks.com>
03/12/2017 13:37, Jerin Jacob:
> On thunderx and octeontx, ring_perf_autotest and
> ring_pmd_perf_autotest test shows better performance
> when disabling CONFIG_RTE_RING_USE_C11_MEM_MODEL.
> On the other hand, Enabling CONFIG_RTE_RING_USE_C11_MEM_MODEL
> shows better performance on thunderx2.
> Since thunderx2 is using the default armv8 config,
> no particular change is required.
>
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Applied, thanks
prev parent reply other threads:[~2018-01-29 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 12:37 Jerin Jacob
2018-01-29 15:14 ` 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=1749775.YaGPC7JKFg@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jia.he@hxt-semitech.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).