From HP-SEE Wiki

Revision as of 13:45, 17 June 2011 (view source) Roczei (Talk | contribs) ← Older edit		Revision as of 13:13, 23 August 2011 (view source) Roczei (Talk | contribs) (→Recommendations for Configuration and Usage) Newer edit →
Line 71:		Line 71:
	== Recommendations for Configuration and Usage ==		== Recommendations for Configuration and Usage ==
-
-	Please describe here any common settings, configurations or conventions that would make the usage of this resource (library or tool) more interoperable or scalable across the HP-SEE resources. These recommendations should include anything that is related to the resource and is agreed upon by administrators and users, or across sites and applications. These recommendations should emerge from questions or discussions opened by site administrators or application developers, at any stage, including installation, development, usage, or adaptation for another HPC centre.
-
-	Provided descriptions should describe general or site specific aspects of resource installation, configuration and usage, or describe the guidelines or convention for deploying or using the resource within the local (user/site) or temporary environment (job). Examples are:
-
-	* Common configuration settings of execution environment
-	* Filesystem path or local access string
-	* Environment variables to be set or used by applications
-	* Options (e.g. additional modules) that are needed or required by applications and should be present
-	* Minimum quantitative values (e.g. quotas) offered by the site
-	* Location and format of some configuration or usage hint instructing applications on proper use of the resource or site specific policy
-	* Key installation or configuration settings that should be set to a common value, or locally tweaked by local site admins
-	* Conventions for application or job bound installation and usage of the resource

---

Revision as of 13:13, 23 August 2011

Contents 1 Information 1.1 Authors/Maintainers 1.2 Summary 1.3 Features 1.4 Architectural/Functional Overview 1.5 Usage Overview 1.6 Dependacies 1.7 HP-SEE Applications 1.8 Resource Centers 1.9 Resource Centers 1.10 Usage by other projects and communities 1.11 Recommendations for Configuration and Usage

Information

• Web site: http://www.netlib.org/blacs/
• Described version: 1.1
• Licensing: Free (not explicitly defined)
• User documentation: http://www.netlib.org/blacs/lawn94.ps
• Download: http://www.netlib.org/blacs/archives/
• Source code: PVM, MPI + patch

Authors/Maintainers

• The General in this project is Jack Dongarra; the man in the trenches is R. Clint Whaley. Questions about the BLACS should be mailed to scalapack@cs.utk.edu or on the ScaLAPACK User Forum

Summary

The BLACS (Basic Linear Algebra Communication Subprograms) is a package that attempts to provide the same ease of use and portability for distributed memory linear algebra communication that the BLAS provide for linear algebra computation. The concept of concentrating the most used computation into a kernel of highly optimized routines, such as the BLAS, has proven itself in work on LAPACK. LAPACK (Linear Algebra PACKage) provides linear algebra routines for sequential and shared memory machines. There are various packages designed to provide a message passing interface that remains unchanged across multiple platforms, including PICL, PVM and more recently, MPI. These packages are general libraries, however, and thus their interfaces are not as easily usable for linear algebra applications as we would like. The goals of the BLACS project include:

• Ease of programming. Wherever possible, the BLACS will simplify message passing in order to reduce programming errors.
• Ease of use. The interface to the BLACS will be at such a level as to be easily usable by linear algebra programmers.
• Portability. The BLACS must supply an interface which can be supported across a Wide range of parallel computers, including parallel machines built from heterogeneous processors.

This user's guide is supplemented by the BLACS web page. The URL is http://www.netlib.org/blacs/Blacs.html. This on-line document gives detailed examples, as well as providing reference, downloading options, installation instructions, and troubleshooting. If problems still remain after reading this guide and consulting the mosaic page, questions should be mailed to blacs@cs.utk.edu. With distributed memory machines, the basic unit of execution is referred as a process. A process is a thread of execution which minimally includes a stack, registers, and memory. Multiple processes may share a processor. The term processor refers to the actual hardware. In the BLACS, each process is treated as if it were a processor: the process must exist for the lifetime of the BLACS run, and its execution should only affect other processes' execution through the use of message passing calls. The BLACS source code was contributed by many before FOSS licenses were established; there are both free and commercial versions/implementations available.

Features

• Array-based communication
• Process Grid and scoped operations
• ID-less communication
• Blocking levels

Architectural/Functional Overview

• high level design info, how it works, performance - may be a link, or several links

Usage Overview

• Quick Reference Guide to the C and Fortran 77 interface for the BLACS.

Dependacies

• C or Fortran 77
• MPI or PVM

HP-SEE Applications

• HMLQCD (Hadron Masses from Lattice QCD)

Resource Centers

• University of Tirana, Albania

Resource Centers

• BG, BG
• HPCG, BG
• NIIFI SC, HU
• PARADOX, RS

Usage by other projects and communities

• If any

Recommendations for Configuration and Usage