Result for 1D6A2BE3EE95A703C6F84D811B9D063E58F88870

Query result

Key Value
FileName./usr/lib/pmix/mca_psquash_flex128.so
FileSize15644
MD59377DDE542333F36FE119ECE0AAFDD20
SHA-11D6A2BE3EE95A703C6F84D811B9D063E58F88870
SHA-256A5AFE51F5632E8B343994F942188BA68925B62F9E8B2BD6A7C95698541E4A40B
SSDEEP96:lP0l5zGBWBrYqkwYmLffz0+JtPIxO+gz12fotnkcxK/hhDpBgTnWR3ij8nQn5Jey:50fG8BYq3FjpfzIOk5VBeWRiInQT
TLSHT11762188ABBA3DEB3E151873406DBCF3461BAC4220582C75BAA60FA6D3CE36C45D13654
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
MD57188C80292E064938BDA34A1C642D1F8
PackageArchi686
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.
PackageMaintainerFedora Project
PackageNamepmix
PackageRelease1.fc34
PackageVersion3.2.3
SHA-156CFB513E1C4DCE9AFD90AD84467F12D603C7EE8
SHA-2563F810DD00332BE062F54DDF09D2DAE243C345E62DF37016F5C974C8138FE8135