lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Sun, 8 Jan 2012 16:12:24 +0100
From:	Jan-Erik Lange <jan0385@...mail.de>
To:	<linux-kernel@...r.kernel.org>
Subject: IPC implementation in Linux


Hello,
 
I have a question concerning the implementation of the IPC mechanisms in Linux. Unfortunately I didn't find any further information in the web.
 
1. There is the Shared memory mechanism: So far as I know it maps some processes address space to the address space
of another process. Through this address space the two processes can exchange information. This way of IPC is quite replicable 
for me.
 
2. But how are the IPC mechanisms like message queues or pipes/FIFOs realized? Are they workng with a shared address space too?
 
Best regards
 
Jan 		 	   		  --
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ