Mellanox Technologies --------------------- ============================================================= = Mellanox ScalableUPC Release Notes = = Version 2.2 = = Last Modified on December 15, 2012 = ============================================================= -------------------------------------------------------------- NOTE: THIS HARDWARE, SOFTWARE OR TEST SUITE PRODUCT (“PRODUCT(S)”) AND ITS RELATED DOCUMENTATION ARE PROVIDED BY MELLANOX TECHNOLOGIES “AS-IS” WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PRODUCTS IN DESIGNATED SOLUTIONS. THE CUSTOMER'S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCTO(S) AND/OR THE SYSTEM USING IT. THEREFORE, MELLANOX TECHNOLOGIES CANNOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED. IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT, INDIRECT, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING, BUT NOT LIMITED TO, PAYMENT FOR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY FROM THE USE OF THE PRODUCT(S) AND RELATED DOCUMENTATION EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. -------------------------------------------------------------- © Copyright 2012. Mellanox Technologies. All rights reserved Mellanox®, BridgeX®, ConnectX®, CORE-Direct®, InfiniBlast®, InfiniBridge®, InfiniHost®, InfiniRISC®, InfiniScale®, InfiniPCI®, PhyX®, SwitchX®, UFM®, Virtual Protocol Interconnect®, and Voltaire® are registered trademarks of Mellanox Technologies, Ltd. Connect-IB™, FabricIT™, MetroX™, MLNX-OS™, Unbreakable-Link™, UFM™ and Unified Fabric Manager™ are trademarks of Mellanox Technologies, Ltd. All other marks and names mentioned herein may be trademarks of their respective companies. Contents ======== 1. Overview 2. Changes in This Release 3. Supported Platforms and Operating Systems 4. Known Issues =============================================================================== 1. Overview =============================================================================== These are the release notes for the Mellanox ScalableUPC 2.2. Mellanox ScalableUPC is based on Berkeley UPC (BUPC) version 2.16.0. - Berkeley UPC project web site: http://upc.lbl.gov - Berkeley UPC documentation is avalable here: http://upc.lbl.gov/docs - Lastest Berkeley UPC release, as well as installation instructions are available for download here: http://upc.lbl.gov/download =============================================================================== 2. Changes in This Release =============================================================================== ScalableUPC v2.2 Main Changes from v2.1 (from Berkeley UPC version 2.16.0): ------------------------------------------------------------------------------- The following list contains only the changes that were done on top of the original Berkeley UPC version 2.16.0, that is available for download from the UC Berkeley/LBNL web site: http://upc.lbl.gov/download/release/berkeley_upc-2.16.0.tar.gz - Linking with FCA library instead of using dlopen at runtime. - Fixed an issue using some of MPIs as job spawner (e.g. MPICH2) Use MPI_BYTE rather than MPI_CHAR, and use MPI_IN_PLACE. =============================================================================== 3. Supported Platforms and Operating Systems =============================================================================== Summary of changes in the list of supported OSes: - Platforms: - x86_64 - Operating Systems: - RHEL 6.2 - OFED: - MLNX_OFED 1.8.5 or higher =============================================================================== 4. Known Issues =============================================================================== - Currently, the UPC Barrier does not utilize FCA Barrier, so while GASNET_FCA_ENABLE_BARRIER option that enables/disabled the FCA barrier does affect various UPC collectives, it does not affect UPC Barrier.