Result for 1617F02C57D839BDCB4CA7ADAF57E1903882554A

Query result

Key Value
FileName./usr/share/man/man3/Coro::Semaphore.3pm.gz
FileSize2675
MD5E4DAA25E54686ACDDF9F9519BA753B70
SHA-11617F02C57D839BDCB4CA7ADAF57E1903882554A
SHA-256A87EE95D7FD83F77F3BE4C2289E632D3D9E2B57024F3F0E3112DF3E708413DC0
SSDEEP48:XwISuG5dDOeaJyYkKSBfpH6nISOyIoSS//SGe8V0SZvLB9nWVXem0fDYxzLw8NVe:gIJG5dbGMVcISnT//SGe8WSZvfWhUDYo
TLSHT180516E3745B197F0470D3EBF0ABB4021501708560C1992519F8F7257C774A823BFEDA9
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
MD56F08827CBB87909DE56F05A732332CC1
PackageArchi586
PackageDescriptionFor a tutorial-style introduction, please read the Coro::Intro manpage. This manpage mainly contains reference information. This module collection manages continuations in general, most often in the form of cooperative threads (also called coros, or simply "coro" in the documentation). They are similar to kernel threads but don't (in general) run in parallel at the same time even on SMP machines. The specific flavor of thread offered by this module also guarantees you that it will not switch between threads unless necessary, at easily-identified points in your program, so locking and parallel access are rarely an issue, making thread programming much safer and easier than using other thread models. Unlike the so-called "Perl threads" (which are not actually real threads but only the windows process emulation (see section of same name for more details) ported to UNIX, and as such act as processes), Coro provides a full shared address space, which makes communication between threads very easy. And coro threads are fast, too: disabling the Windows process emulation code in your perl and using Coro can easily result in a two to four times speed increase for your programs. A parallel matrix multiplication benchmark (very communication-intensive) runs over 300 times faster on a single core than perls pseudo-threads on a quad core using all four cores. Coro achieves that by supporting multiple running interpreters that share data, which is especially useful to code pseudo-parallel processes and for event-based programming, such as multiple HTTP-GET requests running concurrently. See Coro::AnyEvent to learn more on how to integrate Coro into an event-based environment. In this module, a thread is defined as "callchain + lexical variables + some package variables + C stack), that is, a thread has its own callchain, its own set of lexicals and its own set of perls most important global variables (see Coro::State for more configuration and background info). See also the 'SEE ALSO' section at the end of this document - the Coro module family is quite large.
PackageNameperl-Coro
PackageRelease1.43
PackageVersion6.57
SHA-1966823564735855049C329A51E09209D85CE076D
SHA-256721AED1664DA2BE7ECD9ABCCBF8930B10E7007AFC265ED8FAB46002C08764FEF
Key Value
MD51B18280D89728CE96945EFCF9446DBBF
PackageArchx86_64
PackageDescriptionFor a tutorial-style introduction, please read the Coro::Intro manpage. This manpage mainly contains reference information. This module collection manages continuations in general, most often in the form of cooperative threads (also called coros, or simply "coro" in the documentation). They are similar to kernel threads but don't (in general) run in parallel at the same time even on SMP machines. The specific flavor of thread offered by this module also guarantees you that it will not switch between threads unless necessary, at easily-identified points in your program, so locking and parallel access are rarely an issue, making thread programming much safer and easier than using other thread models. Unlike the so-called "Perl threads" (which are not actually real threads but only the windows process emulation (see section of same name for more details) ported to UNIX, and as such act as processes), Coro provides a full shared address space, which makes communication between threads very easy. And coro threads are fast, too: disabling the Windows process emulation code in your perl and using Coro can easily result in a two to four times speed increase for your programs. A parallel matrix multiplication benchmark (very communication-intensive) runs over 300 times faster on a single core than perls pseudo-threads on a quad core using all four cores. Coro achieves that by supporting multiple running interpreters that share data, which is especially useful to code pseudo-parallel processes and for event-based programming, such as multiple HTTP-GET requests running concurrently. See Coro::AnyEvent to learn more on how to integrate Coro into an event-based environment. In this module, a thread is defined as "callchain + lexical variables + some package variables + C stack), that is, a thread has its own callchain, its own set of lexicals and its own set of perls most important global variables (see Coro::State for more configuration and background info). See also the 'SEE ALSO' section at the end of this document - the Coro module family is quite large.
PackageNameperl-Coro
PackageRelease1.43
PackageVersion6.57
SHA-101D10398D8337F04BB237FB89F6B2A589B770FC0
SHA-256705730C2EA81D4A7AF709E9D1AAFA8D8EE9D8BC6C8D14125E8CC65675876065A