public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: floaterions <floaterions-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: RDMA atomic operations fail
Date: Sun, 28 Dec 2014 12:13:35 +0200	[thread overview]
Message-ID: <20141228101335.GC1806@mtldesk30> (raw)
In-Reply-To: <loom.20141224T040342-951-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>

On Wed, Dec 24, 2014 at 03:08:45AM +0000, floaterions wrote:
> When I try to submit an RDMA FETCH_AND_ADD or CMP_AND_SWAP ,
> the ibv_post_send() function fails, with Errno set to "Invalid argument".
> I have no such problems with RDMA READ/WRITE. 
> 
> I developed my entire code using RDMA CM (so no manual QP transitioning). 
> The queue pair is RC, and Atomic is enabled at the responder queue pair,
> and the memory regions are registered with atomic access.
> 
> I suspected that there might be the source of this problem,
> so I wrote a small program using libibcm where I transition the QPs manually
> and set the flags fro atomic operations:
> qp_attr->qp_access_flags = IBV_ACCESS_REMOTE_ATOMIC; 
> qp_attr->max_rd_atomic = <something greater than zero>; 
> qp_attr->max_dest_rd_atomic = <something greater than zero>; 
> 
> But still, the same error (invalid argument).
> 

Hi,
the current code in upstream does not support atomic operations.
Patches were sent already that will allow to use atomic operations
over mlx5 supported devices.

For now, if you query the HCA capabilites you should get ATOMIC_NONE
at the atomic_cap field when you query the device capabilites.
--
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:[~2014-12-28 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  3:08 RDMA atomic operations fail floaterions
     [not found] ` <loom.20141224T040342-951-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2014-12-25  8:42   ` Sagi Grimberg
     [not found]     ` <CAJRcJr1QKB-7=xx6fD80RjfikR5ZJU+_6WTidXwCB-CocsPqzA@mail.gmail.com>
     [not found]       ` <CAJRcJr1QKB-7=xx6fD80RjfikR5ZJU+_6WTidXwCB-CocsPqzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-28  9:59         ` Sagi Grimberg
2014-12-28 10:13   ` Eli Cohen [this message]
2014-12-29  1:26     ` Just Floaterions

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=20141228101335.GC1806@mtldesk30 \
    --to=eli-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=floaterions-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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