ibacm-devel-1.0.9-1.el6>t  DH`pU/ FzIFԦedQ)91u;QåNd9Џ-{%j稤:NwMSTғXJ䢊myxb>U뙋r#%:EaOy^s?;hL祊cŒ8jN'\ :$VHw@Ycd%n&dF' WY_6@ |Xv8/.QV։_;=R^|-dRsJF߻s͙Giը('@-0 ~df>&\}e3jZ F'+OΙ/`c8ka9d#@J^?>ǚ_TĬdd)i ^:2h4) qݘ׍YNb2887821e751cabed770159d5d3aded71d7abc30U/ F#Z)쭫'd=BXJυ#`c&B)N gbY8cEdz@`kTLH&$O=^Ʋ$x߉9nh obU8hIxKPW@n]ufh?(j9Pcj8hJ-E/h`}x~@+S SŊq2нwET-yG2<{ %AC{ԤRA k}"dZ@M嚇u/ =m9xY]~BFիʍ_BuoSmUr]d|o㑒!>I#W 2Z j&$giKQwpitPn7%`}p Re] yT|ϗ`7 ? xd  \$(/<h      $(H\(89 :0G <H @I DX HY P\ h] l^ rb d )e .f 1l 3t Lu Pv Tw lx p tCibacm-devel1.0.91.el6Headers file needed when building apps to talk directly to ib_acmMost applications do not need to know how to talk directly to the ib_acm daemon, but it does have a socket that it listens on, and it has a specific protocol for incoming/outgoing data. So if you wish to build the ability to communicate directly with ib_acm into your own application, the protocol used to communicate with it, and the data structures involved, are in this header file. Please note that this is an unsupported method of using this daemon. The only supported means of using this is via librdmacm. As such, even though this header file is provided, no further documentation is available. One must read the source if they wish to make use of this header file.Uyc6b8.bsys.dev.centos.orgCentOSGPLv2 or BSDCentOS BuildSystem System Environment/Daemonshttps://www.openfabrics.org/linuxi686Uy5baf0cfcc2ea1132b79767012e98e8782ea32b3b43f4d36bb8f5721a07ac1c30rootrootibacm-1.0.9-1.el6.src.rpmibacm-develibacm-devel(x86-32)    ibacmrpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)1.0.9-1.el63.0.4-14.6.0-14.0-15.2-14.8.0U.@S@P{O}@O}@OLDoug Ledford - 1.0.9-1Doug Ledford - 1.0.9-0.git3cbbe4eDoug Ledford - 1.0.8-0.git7a3adb7Doug Ledford - 1.0.5-3Doug Ledford - 1.0.5-2Doug Ledford - 1.0.5-1- Update to official 1.0.9 release - Related: bz1119108- Update to head of git repo to pick up dynamic addressing changes - Resolves: bz1056662- Update to latest upstream via git repo - Resolves: bz866222, bz866223- Until the next upstream release, the pid file is in a wonky location. Make the init script know about that location so we can stop properly. - Resolves: bz808599- Don't install the address file or config file, the config file isn't strictly needed and defaults will be used if it isn't installed, but with the address file we specifically need to build one based upon the machine where the program is installed, a default file is not only not helpful, but it messes up the daemon. - Related: bz700285- Ininital version for rhel6 - Related: bz7002851.0.9-1.el61.0.9-1.el6acm.h/usr/include/infiniband/-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tablescpioxz2i686-redhat-linux-gnuASCII textdirectory?7zXZ !PH6+I] b2u Q{J󛻀| H8RĂͳ_Z j4wbͼu@S|HFI1?1"$MSLɥE*˛B b@e9rNe/S&QЂt( ν1 h 7GW(?pSV%~'a ۵5Iծh_n7KQWɺ&`ls-n<\L6STͿj_*W"SޏeCΤv% sҡ H5 SB'8^I`-Šeq0*wcvj3L{̽zH: Ocة`^S[tS7Q\bGk͸lf ?GN;Ѭ#EƇr `dg)*ű#4.zՉZ3{+VyT~X /;ǁwC=Eqrj^i`z\KĴvVH#GI.كARt@2T`e>q&UEB*`CkLtkE8Rcq &MFД;"iejb6]. p Eif 9V̐Z"!IP`=r8r~X<{>Ҧ|ZփtOG޲h>+\m]-mLbfbTT`L"!D<@ؿ7EI0E|G|'?hw7ɘ]XTβsgdeh4Y| 0/wdc^p5k|bjCĵ"{^9]NB8P8xll:*VRp\o0X}:܊^qDI8:1aFVҬTVg*M&uBdɢ7a5c,uζa|Po˗;zK2[BHMoVU`>?`8#e 3nihZTÛYxGZ㴡MMv@J}