public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Sokolovsky <vlad-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: "Håkon Bugge" <Haakon.Bugge-UdXhSnd/wVw@public.gmane.org>
Cc: rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V4 1/2] IB/core: Add support for enhanced atomic operations
Date: Tue, 20 Apr 2010 16:36:42 +0300	[thread overview]
Message-ID: <4BCDADEA.1090105@dev.mellanox.co.il> (raw)
In-Reply-To: <BE945405-03B6-4D5F-8DC8-A7424250BDEC-U0mLk4xYmo8@public.gmane.org>

Håkon Bugge wrote:
> On Apr 14, 2010, at 16:23 , Vladimir Sokolovsky wrote:
> 
>> The additional operands are carried in the Extended Transport Header
> 
> Is this a newly defined ETH which follows the AETH on the wire?
> 
> 
> 
> Thanks, Håkon
> 

Yes,
Atomic masked Fetch and Add uses first 64 bits to provide the date to add,
and the second 64 bits provide the field boundary:

Swap (or Add) data high [63:32]
Swap (or Add) data low  [31:0]
Compare data (or Field boundary) high [63:32]
Compare data (or Field boundary) high [31:0]

Atomic masked Compare and Swap uses:

Swap (or Add) data high [63:32]
Swap (or Add) data low  [31:0]
Compare data high [63:32]
Compare data high [31:0]
Swap mask high [63:32]
Swap mask low  [31:0]
Compare mask high [63:32]
Compare mask low  [31:0]


Regards,
Vladimir
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-04-20 13:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 14:23 [PATCH V4 1/2] IB/core: Add support for enhanced atomic operations Vladimir Sokolovsky
2010-04-19  8:18 ` Håkon Bugge
     [not found]   ` <BE945405-03B6-4D5F-8DC8-A7424250BDEC-U0mLk4xYmo8@public.gmane.org>
2010-04-20 13:36     ` Vladimir Sokolovsky [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=4BCDADEA.1090105@dev.mellanox.co.il \
    --to=vlad-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=Haakon.Bugge-UdXhSnd/wVw@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.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