All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sean Hefty" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: 'Vladimir Sokolovsky'
	<vlad-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
	Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: [PATCH 1/2] IB/core: Add support for enhanced atomic operations
Date: Wed, 10 Feb 2010 16:51:56 -0800	[thread overview]
Message-ID: <96930957548D41E0B47FA465CAAD05E6@amr.corp.intel.com> (raw)
In-Reply-To: <20100201155959.GA17341@vlad-laptop>

> enum ib_atomic_cap {
>@@ -472,7 +473,9 @@ enum ib_wc_opcode {
>  * receive by testing (opcode & IB_WC_RECV).
>  */
> 	IB_WC_RECV			= 1 << 7,
>-	IB_WC_RECV_RDMA_WITH_IMM
>+	IB_WC_RECV_RDMA_WITH_IMM,
>+	IB_WC_MASKED_COMP_SWAP,
>+	IB_WC_MASKED_FETCH_ADD
> };

This breaks the ability to check for a receive by testing opcode & IB_WC_RECV.
Is it even necessary to define new work completion opcodes?

> enum ib_wc_flags {
>@@ -689,6 +692,8 @@ enum ib_wr_opcode {
> 	IB_WR_RDMA_READ_WITH_INV,
> 	IB_WR_LOCAL_INV,
> 	IB_WR_FAST_REG_MR,
>+	IB_WR_ATOMIC_MASKED_CMP_AND_SWP,
>+	IB_WR_ATOMIC_MASKED_FETCH_AND_ADD,
> };

Just tossing this out as a possibility -- the mask itself could be used to
indicate the type of operation.  Kernel clients would always set the mask for
all atomic operations.

Also, is there a kernel user for this functionality?

- Sean

--
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

  reply	other threads:[~2010-02-11  0:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 15:59 [PATCH 1/2] IB/core: Add support for enhanced atomic operations Vladimir Sokolovsky
2010-02-11  0:51 ` Sean Hefty [this message]
     [not found]   ` <96930957548D41E0B47FA465CAAD05E6-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-02-11 13:48     ` Vladimir Sokolovsky
2010-02-17 18:49     ` Andy Grover
     [not found]       ` <4B7C3A2C.6070202-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-02-17 23:56         ` Richard Frank

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=96930957548D41E0B47FA465CAAD05E6@amr.corp.intel.com \
    --to=sean.hefty-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
    --cc=vlad-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.