Result for 2025E8D238E0F0E240A75D6389A5466499025BEC

Query result

Key Value
FileName./usr/bin/pmix_info
FileSize40868
MD5D01F75AC5E85097E22E2EEF5A3658C5F
SHA-12025E8D238E0F0E240A75D6389A5466499025BEC
SHA-256549CBE4ED58AC32307E0800175DEB157AAA9A92EED83EFB26EC778873CA0155F
SSDEEP768:IHiVAe5gj7aAxb0/PvUJYd2HmAEdMSaiaEEuOlHeL7kjNeWYFCZLqCuBO9lQH2L:RVRrMSaisuOlHKd8ZLqHBOPL
TLSHT1B4031A0AA29BCC71F9224AB8E757965134725049E18FEAF0D70DAF60B47E644BF0B335
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5C7DFFF8E1BAFCFD9538A9B80D110029D
PackageArchi586
PackageDescriptionThe Process Management Interface (PMI) has been used for quite some time as a means of exchanging wireup information needed for interprocess communication. Two versions (PMI-1 and PMI-2) have been released as part of the MPICH effort. While PMI-2 demonstrates better scaling properties than its PMI-1 predecessor, attaining rapid launch and wireup of the roughly 1M processes executing across 100k nodes expected for exascale operations remains challenging. PMI Exascale (PMIx) represents an attempt to resolve these questions by providing an extended version of the PMI standard specifically designed to support clusters up to and including exascale sizes. The overall objective of the project is not to branch the existing pseudo-standard definitions - in fact, PMIx fully supports both of the existing PMI-1 and PMI-2 APIs - but rather to (a) augment and extend those APIs to eliminate some current restrictions that impact scalability, and (b) provide a reference implementation of the PMI-server that demonstrates the desired level of scalability.
PackageMaintainereatdirt <eatdirt>
PackageNameopenpmix
PackageRelease1.mga9
PackageVersion4.2.0
SHA-17AAF01CF2F5F62AA395567280343B529724BDF6A
SHA-2562C19EDF1114D2398777B4E235541BD3631C7A23823825B03BCEFB111AFCB137A