From: Olivier MATZ <olivier.matz@6wind.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [memnic PATCH] pmd: use rte_atomic32_cmpset instead of cmpxchg
Date: Fri, 11 Apr 2014 11:37:13 +0200 [thread overview]
Message-ID: <2202149.SQVFq2HVaI@platinum> (raw)
In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD0109D67F@BPXM14GP.gisp.nec.co.jp>
On Thursday, April 03, 2014 07:34:56 AM Hiroshi Shimamoto wrote:
> From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>
> Because DPDK has its own compare and set function to optimize to
> dedicated processor type, use that rte_atomic32_cmpset() instead of
> cmpxchg macro which is specially introduced for MEMNIC.
>
> Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> ---
> common/memnic.h | 12 ------------
> pmd/pmd_memnic.c | 10 ++++++----
> 2 files changed, 6 insertions(+), 16 deletions(-)
Reviewed-by: Olivier Matz <olivier.matz@6wind.com>
next prev parent reply other threads:[~2014-04-11 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 7:34 Hiroshi Shimamoto
2014-04-11 9:37 ` Olivier MATZ [this message]
2014-04-11 15:45 ` 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=2202149.SQVFq2HVaI@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
/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).