From: Hagen Paul Pfeifer <hagen@jauu.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Process Communication Mechanisms
Date: Fri, 11 Aug 2006 17:32:39 +0200 [thread overview]
Message-ID: <20060811153239.GA20436@c3po.0xdef.net> (raw)
In-Reply-To: <75fdd94c0608110425w40493f48u2ef6d73ed3f6dec1@mail.gmail.com>
* Kamran Soomro | 2006-08-11 16:25:43 [+0500]:
>Hi. I want to study how the 2.6 kernel handles process communication.
>I am planning to study the source code for this purpose. Can someone
>please guide me as to where to start? And how to proceed. Thanks.
Process Communication in the sense of SYS V? Then the complete ipc directory
[1] will be your friend.
For Unix sockets the implementation is a little bit more complicated - you must
grasp more source-code. But this depends on how deep is your interesting.
Last but not least: there are many books out there who cover this topic.
[1] http://lxr.linux.no/source/ipc/
prev parent reply other threads:[~2006-08-11 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 11:25 Kamran Soomro
2006-08-11 15:32 ` Hagen Paul Pfeifer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060811153239.GA20436@c3po.0xdef.net \
--to=hagen@jauu.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®