DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org, Olivier MATZ <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [memnic PATCH] pmd: use rte_atomic32_cmpset instead of cmpxchg
Date: Fri, 11 Apr 2014 17:45:38 +0200	[thread overview]
Message-ID: <14708439.90U7M7f90D@xps13> (raw)
In-Reply-To: <2202149.SQVFq2HVaI@platinum>

2014-04-11 11:37, Olivier MATZ:
> 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>
> 
> Reviewed-by: Olivier Matz <olivier.matz@6wind.com>

Applied

Thanks
-- 
Thomas

      reply	other threads:[~2014-04-11 15:44 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
2014-04-11 15:45   ` 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=14708439.90U7M7f90D@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.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).