From: "lihaidong" <lihaidong-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Steve Wise
<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
Tziporet Koren <tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
shipr <shipr-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
Subject: Mellanox implementation for atomic operations
Date: Mon, 10 May 2010 14:42:27 +0800 [thread overview]
Message-ID: <201005101442273436938@inspur.com> (raw)
In-Reply-To: 201005101435267348378@inspur.com
Hi,
I have a question about atomic operations.
According to IB specification o10-48, all atomic operation request made to the same HCA, referencing the same physical memory are serialized with respect to each other. I know this should be complied with if HCA supports atomic operations, right?
According to IB specification o10-49, all atomic operations requests that referencing the same physical memory are serialized with respect to each other. This means that atomic operations performed by processors should serialized with atomic operations performed by HCAs, too, if they were referencing the same physical memory.
I want to know whether Mellanox implementation for atomic operations comply with o10-49 or not.
if not ,to what extent it comply with the rule?
I also was intrested in how this rule is complied with by others vendors?
2010-05-10
lihaidong
--
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
next parent reply other threads:[~2010-05-10 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201005101435267348378@inspur.com>
2010-05-10 6:42 ` lihaidong [this message]
[not found] ` <201005101442273436938-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-06-15 20:50 ` Mellanox implementation for atomic operations Dotan Barak
[not found] ` <4C17E790.2020900-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-06-16 16:41 ` Ralph Campbell
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=201005101442273436938@inspur.com \
--to=lihaidong-6guaa8visnnqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shipr-6gUaA8visnnQT0dZR+AlfA@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
--cc=tziporet-VPRAkNaXOzVS1MOuV/RT9w@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