From my point of view as well the discussion was about Scalapack and also it was agreed that the case of other libraries, like LAPACK, for which there are tuned versions from Sun, would be resolved with further discussion.
If Sun Studio is also in Opensolaris, as is an ongoing consideration, then there would be two versions of LAPACK in Opensolaris (as well as BLAS, PBLAS, BLACS and Scalapack). I think we need to figure this out together. Probably better to do this in a prior meeting rather than in LSARC. Gregory Rebecca Arney wrote: > Bruce, > > Our discussion was only about ScaLAPACK, not Blas and LAPACK. The > issue of having untuned versions of LAPACK looking like perhaps > recommended libraries for OpenSolaris is a much bigger issue than > untuned ScaLAPACK (which currently is not in Studio but will be). > LAPACK is in Studio (and is a highly tuned version which is what is > expected for Sun systems, for both the customer/user and Sun benefit). > This is the original issue discussed (not the "how to port issue"), and > we have not changed our view that this all requires additional > direction/information be provided to users/downloaders instructing them > on just what they are getting and what other alternatives exist or are > recommended (and why they may be better). The lack of such info may > mean people simply see LAPACK and download it , without knowing to > utilize these same highly tuned libraries that are part of the Sun > Studio package in OpenSolaris (Perflib being the component that provides > BLAS, LAPACK, and in the next release also ScaLAPACK). > > Rebecca > > > On Dec 1, 2008, at 9:10 AM, Bruce Rothermal wrote: > >> Hi Terry >> >> The process to integrate these (Blas, LAPACK and ScaLAPACK) has >> already been approved by Rebecca Arney and Jasmine Ocegueda following >> the same process used by Sun Studio to be integrated to OpenSolaris. >> >> So please check with Rebecca and remove your objection. >> >> Thank you >> >> Bruce >> >> On Nov 26, 2008, at 10:09 AM, Terry Dontje wrote: >> >>> On behalf of the Perflib I'd like to derail or at least suspend the >>> timeout for this fast-track. The Perflib group already delivers >>> LAPACK as a part of their product which was ARCd as a part of cases >>> LSARC/1995/406 and 1999/489. I worry that the delivery of the below >>> fast-track might have some interfering consequences for our >>> customers. I believe the Perflib group and the group submitting this >>> fast-track need to resolve the issue of what our customers see when >>> both versions of LAPACK are installed. >>> There are actually a few similar instances of this (SCALAPACK is >>> another) that could really benefit the resolutions of dual packages >>> delivering the same API at different levels of optimization and support. >>> >>> --td >>> >>> John Fischer wrote: >>>> Template Version: @(#)sac_nextcase %I% %G% SMI >>>> This information is Copyright 2008 Sun Microsystems >>>> 1. Introduction >>>> 1.1. Project/Component Working Name: >>>> LAPACK >>>> 1.2. Name of Document Author/Supplier: >>>> Author: Bruce Rothermal >>>> 1.3 Date of This Document: >>>> 25 November, 2008 >>>> 4. Technical Description >>>> 1.0 Project Information >>>> 1.1 Name of project/component >>>> >>>> LAPACK >>>> >>>> 1.2 Author of document >>>> >>>> Bruce Rothermal >>>> >>>> 2.0 Project Summary >>>> 2.1 Project Description >>>> >>>> Port LAPACK Opensource utility to SFW consolidation. Linear Algebra >>>> package. >>>> LAPACK provides routines for solving systems of simultaneous >>>> linear equations, least-squares solutions of linear systems of >>>> equations, eigenvalue problems, and singular value problems. The >>>> associated matrix >>>> factorizations (LU, Cholesky, QR, SVD, Schur, generalized Schur) >>>> are also provided, as are related computations such as reordering >>>> of the Schur factorizations and estimating condition numbers. >>>> Dense and banded matrices are handled, but not general sparse >>>> matrices. In all areas, similar functionality is provided for real >>>> and complex matrices, in both single and double precision. >>>> >>>> 2.2 Release binding >>>> What is is the release binding? >>>> (see >>>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>>> [ ] Major >>>> [x ] Minor >>>> [ ] Patch or Micro >>>> [ ] Unknown -- ARC review required >>>> >>>> 2.3 Type of project >>>> Is this case a Linux Familiarity project? >>>> [ ] Yes >>>> [x ] No >>>> >>>> 2.4 Originating Community >>>> 2.4.1 Community Name >>>> LAPACK >>>> http://www.netlib.org/lapack/ >>>> >>>> 2.4.2 Community Involvement >>>> Indicate Sun's involvement in the community >>>> [ ] Maintainer >>>> [ ] Contributor >>>> [x ] Monitoring >>>> Will the project team work with the upstream community to >>>> resolve >>>> architectural issues of interest to Sun? >>>> [x ] Yes [ ] No - briefly explain >>>> Will we or are we forking from the community? >>>> [ ] Yes - ARC review required prior to forking >>>> [x ] No >>>> 3.0 Technical Description >>>> 3.1 Installation & Sharable >>>> 3.1.1S Solaris Installation - section only required for Solaris >>>> Software >>>> (see >>>> http://opensolaris.org/os/community/arc/policies/install-locations/ >>>> for details) >>>> Does this project follow the Install Locations best practice? >>>> [x ] Yes [ ] No - ARC review required >>>> Does this project install into /usr under >>>> [sbin|bin|lib|include|man|share]? >>>> [x ] Yes >>>> [ ] No or N/A >>>> Does this project install into /opt? >>>> [ ] Yes - explain below >>>> [x ] No or N/A >>>> Does this project install into a different directory >>>> structure? >>>> [ ] Yes - ARC review required >>>> [x ] No or N/A >>>> Do any of the components of this project conflict with >>>> anything under /usr? >>>> (see http://opensolaris.org/os/community/arc/caselog/2007/047/ >>>> for details) >>>> [ ] Yes - explain below >>>> [x ] No >>>> If conflicts exist then will this project install under >>>> /usr/gnu? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [x ] N/A >>>> Is this project installing into /usr/sfw? >>>> [ ] Yes - ARC review required >>>> [x ] No >>>> 3.1.1W Windows Installation - section only required for >>>> Windows Software >>>> (see http://sac.sfbay/WSARC/2002/494 for details) >>>> Does this project install software into a <system >>>> drive>:\Program Files\Sun\<product> or <system drive>:\Sun\<product> >>>> directory? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> Does the project use the Windows registry? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> Does the project use >>>> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product>\<version> >>>> for the registry key? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> Is the project's stored location >>>> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product >>>> id>\<version id>\Path? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> 3.1.2 Share and Sharable >>>> Does the module include any components that are used or shared >>>> by other projects? >>>> [ ] Yes >>>> [x ] No >>>> If yes are these components packaged to be shared with the >>>> other FOSS? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [x ] N/A >>>> Are these components already in the Solaris WOS? >>>> [ ] Yes >>>> [x ] No - continue with next section (section 3.2) >>>> If yes are these newer versions being delivered? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> If yes are the newer versions replacing the existing >>>> versions? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> 3.2 Exported Libraries >>>> Are libraries being delivered by this project? >>>> [x ] Yes >>>> [ ] No - continue with next section (section 3.3) >>>> Are 64-bit versions of the libraries being delivered? >>>> [x ] Yes >>>> [ ] No - ARC review required >>>> Are static versions of the libraries being delivered? >>>> [x ] Yes - ARC review required >>>> [ ] No The package as is only generates static >>>> libraries. I would have to change the opensource package to >>>> make it generate dynamic. >>>> >>>> 3.3 Services and the /etc Directory >>>> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>>> Does the project integrate anything into /etc/init.d or >>>> /etc/rc?.d? >>>> [ ] Yes - ARC review required >>>> [x ] No >>>> Does the project integrate any new entries into >>>> /etc/inittab or >>>> /etc/inetd.conf? >>>> [ ] Yes - ARC review required >>>> [X ] No >>>> >>>> Does the project integrate any private non-public files into >>>> /etc/default >>>> or /etc/ configuration files? >>>> [ ] Yes - ARC review required >>>> [x ] No >>>> >>>> Does the service manifests method context grant rights above that >>>> of the noaccess user and basic privilege set? >>>> [ ] Yes - ARC review required >>>> [x ] No >>>> >>>> 3.4 Security >>>> 3.4.1 Secure By Default (see >>>> http://opensolaris.org/os/community/arc/policies/secure-by-default/ >>>> for details) >>>> (see >>>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ >>>> for details) >>>> (see parts of >>>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >>>> addtional details) >>>> Are there any network services provided by this project? >>>> [ ] Yes >>>> [x ] No - continue with the next section (section 3.4.2) >>>> Are network services enabled by default? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> [ ] N/A >>>> Are network services automatically enabled by the project >>>> during installation? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> [ ] N/A >>>> Are inbound network communications denied by default? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> Is inbound data checked to prevent content-based attacks? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> Is the outbound receiver authenticated? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> Is the receiver authenticated prior to receiving any >>>> sensitive outbound communication? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> 3.4.2 Authorization >>>> (see >>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >>>> >>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>> and >>>> >>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>> for details) >>>> Are there any setuid/setgid privileged binaries in the project? >>>> [ ] Yes - ARC review required >>>> [x ] No - continue with next section (section 3.4.3) >>>> If yes then are the setuid/setgid privileges handled by >>>> the use of roles? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> 3.4.3 Auditing >>>> (see >>>> http://opensolaris.org/os/community/arc/policies/audit-policy/ for >>>> details) >>>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>>> for details) >>>> Does this component contain administrative or security >>>> enforcing software? >>>> [ ] Yes - ARC review required >>>> [x ] No - continue to next section (section 3.4.4) >>>> (see >>>> http://opensolaris.org/os/community/arc/caselog/2003/397 for details) >>>> Do the components create audit logs detailing what took place >>>> including what event >>>> took place, who was involved, when the event took place? >>>> [ ] Yes - ARC contract and Audit project team review required >>>> [ ] No - ARC review required >>>> 3.4.4 Authentication >>>> (see http://opensolaris.org/os/community/arc/policies/PAM/) >>>> Do the components contain any authentication code? >>>> [ ] Yes >>>> [x ] No - continue to next section (section 3.4.5) >>>> If yes do the components use PAM (plugable authentication >>>> modules) for authentication? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> If yes is a single PAM session maintained during >>>> authentication? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> If yes are the components sufficiently privileged to >>>> allow the requested operations (authentication, password >>>> change, process credential manipulation, audit state >>>> initialization)? >>>> [ ] Yes - briefly describe below >>>> [ ] No - ARC review required >>>> 3.4.5 Passwords >>>> (see >>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ >>>> and >>>> >>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >>>> for details) >>>> Do any of the components for the project deal with passwords? >>>> [ ] Yes >>>> [x ] No - continue to next section (section 3.4.6) >>>> If yes are these passwords entered via the CLI or >>>> environment? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> Are passwords stored within the file system for the >>>> component? >>>> [ ] Yes >>>> [ ] No - continue to next section (section 3.4.6) >>>> If yes are the permissions on the file such to protect >>>> exposing the password(s)? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> 3.4.6 General Security Questions >>>> (see >>>> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ >>>> for details) >>>> Are there any network protocols used by this project? >>>> [ ] Yes >>>> [x ] No - continue with the next section (section 3.5) >>>> Do the components use standard network protocols? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> Do network services for the project make decisions based >>>> upon user, host or service identities? >>>> [ ] Yes - explain below >>>> [ ] No >>>> [ ] N/A >>>> >>>> Do the components make use of secret information during >>>> authentication and/or >>>> authorization? >>>> [ ] Yes - explain below >>>> [ ] No >>>> [ ] N/A >>>> 3.5 Networking >>>> Do the components access the network? >>>> [ ] Yes >>>> [x ] No - continue with the next section (section 3.6) >>>> If yes do the components support IPv6? >>>> [ ] Yes [ ] No - ARC review required >>>> 3.6 Core Solaris Components >>>> Do the components of this project compete with or duplicate >>>> core Solaris components? >>>> [ ] Yes - ARC review required >>>> [x ] No Examples of Core Solaris Components include >>>> but are not limited to: >>>> Secure By Default >>>> Authorizations >>>> PAM -- Plugable Authentication Module >>>> Privilege >>>> PRM -- Process Rights Management -- Privilege >>>> Audit >>>> xVm -- Virtualization >>>> zones / Solaris Containers >>>> PRM -- Process Rights Management >>>> RBAC -- Role Based Access Control >>>> TX / Trusted Extensions >>>> ZFS >>>> SMF -- Service Management Facility >>>> FMA -- Fault Management Architecture >>>> SCF -- Smart Card Facility >>>> IPsec >>>> 4.0 Interfaces >>>> (see >>>> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ >>>> for details) >>>> 4.1 Exported Interfaces >>>> Interface Name Classification Comments >>>> --------------------------- ------------------- >>>> --------------------------- >>>> SUNWlapack Volatile >>>> lapack libraries for Volatile >>>> for sparc and x86, 32b >>>> and 64b. 4.2 Imported Interfaces >>>> Interface Name Classification Comments >>>> --------------------------- -------------------- >>>> -------------------------- >>>> LAPACK Volatile version 3.2 >>>> >>>> Package compiles with SunStudio f90 no special compiler needed. >>>> Package requires BLAS and intent is to use functionality from Sun >>>> Cluster >>>> Tools. Which is optimized for Solaris. If not the package >>>> contains the opensource BLAS. >>>> >>>> >>>> >>>> 6. Resources and Schedule >>>> 6.4. Steering Committee requested information >>>> 6.4.1. Consolidation C-team Name: >>>> SFW >>>> 6.5. ARC review type: FastTrack >>>> 6.6. ARC Exposure: open >>>> >>>> >>> >> > -- <http://www.sun.com/> *Gregory V. Tarsy Ph.D. *Senior Manager Floating Point & Numerical Computing Fortran & Sun Performance Library 831.515.3163 831.818.2198 (cell) gregory.tarsy at sun.com <gregory.tarsy at sun.com>
