public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Sokolovsky <vlad-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: "Håkon Bugge" <Haakon.Bugge-UdXhSnd/wVw@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V3 0/2] Add support for enhanced atomic operations
Date: Mon, 12 Apr 2010 12:44:31 +0300	[thread overview]
Message-ID: <4BC2EB7F.20804@dev.mellanox.co.il> (raw)
In-Reply-To: <4BA0F623.1050606-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>

Vladimir Sokolovsky wrote:
> Roland Dreier wrote:
>>  > Hence, I think it would be cleaner if a new capability,
>>  > masked_atomic_cap, were introduced, using the original definitions
>>  > (NONE, HCA, GLOB).
>>
>> Vlad, what do you think about that?  The more I think about it, the
>> cleaner this seems to me.  And it doesn't even consume a device
>> capability flag bit, which is a nice bonus.
> 
> Hi Roland,
> Do you propose to use IB_ATOMIC_GLOB instead of IB_ATOMIC_HCA while setting
> atomic capability in the code below?
> 
>         props->atomic_cap          = dev->dev->caps.flags & 
> MLX4_DEV_CAP_FLAG_ATOMIC ?
>                 IB_ATOMIC_HCA : IB_ATOMIC_NONE;
> 
> Or add IB_MASKED_ATOMIC to ib_atomic_cap enum and use this one instead 
> of IB_ATOMIC_HCA?
> 
> All this, of course, comes to replace setting IB_DEVICE_MASKED_ATOMIC 
> for device capability.
> 
> Thanks,
> Vladimir
> 
> 

Hi Roland,
Can you comment?

Thanks,
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-12  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 15:57 [PATCH V3 0/2] Add support for enhanced atomic operations Vladimir Sokolovsky
2010-03-11 17:29 ` Håkon Bugge
     [not found]   ` <A27E2E88-63A0-45EE-9A70-F95B2A0C25AD-U0mLk4xYmo8@public.gmane.org>
2010-03-11 18:59     ` Roland Dreier
     [not found]       ` <adaaaueelby.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-03-12  9:21         ` Håkon Bugge
     [not found]           ` <BA082DF0-B3C6-4405-B480-F69B0193BF17-UdXhSnd/wVw@public.gmane.org>
2010-03-12 15:53             ` Roland Dreier
     [not found]               ` <adavdd1a64g.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-03-16 23:49                 ` Roland Dreier
     [not found]                   ` <adaeijj96a6.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-03-17 15:32                     ` Vladimir Sokolovsky
     [not found]                       ` <4BA0F623.1050606-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-04-12  9:44                         ` Vladimir Sokolovsky [this message]
     [not found]                           ` <4BC2EB7F.20804-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-04-13 17:43                             ` Roland Dreier
2010-03-15  7:25     ` Vladimir Sokolovsky

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=4BC2EB7F.20804@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