Re: [openib-general] basic IB doubt

[mlakshmanan]

Date sent:   Fri, 25 Aug 2006 11:55:55 -0700




From:     "Greg Lindahl" <[EMAIL PROTECTED]>











> For example, on an architecture where you need to do work such as




> flushing the cache before accessing DMAed data, that's done in the




> completion. x86 in general is not such an architecture, but they




> exist. IB is intended to be portable to any CPU architecture.




> 











I presume you meant invalidate the cache, not flush it, before accessing DMA'ed 
data. 











-madhu



___
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Re: [openib-general] Conflicting typedefs for "ib_gid_t"

[mlakshmanan]

>>> I don't think the way forward is using iba/ in all applications.
>>> I see it mostly as a legacy header for opensm and related apps
>>> that want their own layer for portability between stacks.
> > 
> > I agree with your view on iba/ib_types.h

Does that imply that the definitions in iba/ib_types.h are not expected to be 
required or used 
by user-space applications other than those categories mentioned above? If 
iba/ib_types.h is 
only a legacy header, are the definitions also present in another header file?

Madhu


___
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Re: [openib-general] Conflicting typedefs for "ib_gid_t"

[mlakshmanan]

>  
> This is a similar but more mainstream example of the conflicts.  A previous 
> one was reported last week in terms of CM. Still not sure of the best 
> resolution for this.
>  
> Do you really need both includes ?
>  

The userspace tool shows a textual representation of a HCA port's capability 
mask. So it 
requires the port capability bit definitions in ib_types.h. And I require mad.h 
for the MAD API.

> -- Hal

Thanks,

Madhu
> 
> 
> 
> From: [EMAIL PROTECTED] on behalf of Lakshmanan, Madhu
> Sent: Mon 8/14/2006 12:19 PM
> To: openib-general@openib.org
> Subject: [openib-general] Conflicting typedefs for "ib_gid_t"
> 
> 
> 
> 
> 
> In .../include/infiniband/mad.h,  it is:
> 
> typedef uint8_t ib_gid_t[16];
> 
> In .../include/infiniband/iba/ib_types.h, it is:
> 
> #include 
> typedef union _ib_gid
> {
> uint8_t raw[16];
> struct _ib_gid_unicast
> {
> ib_gid_prefix_t prefix;
> ib_net64_t  interface_id;
> 
> } PACK_SUFFIX unicast;
> 
> struct _ib_gid_multicast
> {
> uint8_t header[2];
> uint8_t raw_group_id[14];
> 
> } PACK_SUFFIX multicast;
> 
> } PACK_SUFFIX ib_gid_t;
> #include 
> 
> I need to include both files for a user space tool and I'm getting a compile 
> error due to the conflict. Is it not the norm for a user space application to 
> include both files?
> Appreciate any thoughts on this.
> 
> Madhu Lakshmanan
> Silverstorm Technologies, Inc.
> [EMAIL PROTECTED]  
> 
> ___
> openib-general mailing list
> openib-general@openib.org
> http://openib.org/mailman/listinfo/openib-general
> 
> To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
> 
> 
> 
> 




___
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general