<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>EmbLogic &#187; akansha.agarwal</title>
	<atom:link href="https://www.emblogic.com/blog/author/akansha-agarwal/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.emblogic.com/blog</link>
	<description>Embedded System and ARM Training</description>
	<lastBuildDate>Tue, 03 Mar 2020 13:00:06 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.1</generator>
	<item>
		<title>ipc mechanism using pipes</title>
		<link>https://www.emblogic.com/blog/11/ipc-mechanism-using-pipes/</link>
		<comments>https://www.emblogic.com/blog/11/ipc-mechanism-using-pipes/#comments</comments>
		<pubDate>Mon, 25 Nov 2013 12:15:58 +0000</pubDate>
		<dc:creator><![CDATA[akansha.agarwal]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=7471</guid>
		<description><![CDATA[PROJECT-03(IPC USING PIPES) As per the project-03 class from “IPC”  using “PIPES”.This process is based on IPC technique.It is inter process communication which is create a client server setup.It is a client server programming. There are four types of IPC&#8217;s &#8230; <a href="https://www.emblogic.com/blog/11/ipc-mechanism-using-pipes/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>PROJECT-03(IPC USING PIPES)</p>
<p>As per the project-03 class from “IPC”  using “PIPES”.This process is based on IPC technique.It is inter process communication which is create a client server setup.It is a client server programming.</p>
<p>There are four types of IPC&#8217;s<br />
&gt;&gt;Pipes<br />
&gt;&gt;Fifo&#8217;s<br />
&gt;&gt;MesageQueues<br />
&gt;&gt;Shared Memory</p>
<p>Here it is a low level programming language which it is define as:</p>
<p>&gt;&gt;can operate in resource constraint enviroment<br />
&gt;&gt;run time library<br />
&gt;&gt;It is very efficient<br />
&gt;&gt;memory access and control flow<br />
&gt;&gt;debugging can be difficult it can not be possible to run the program.</p>
<p>PIPES:It use the term pipe when it connect the data flow one  process to another.Generally it attach pipe the output of the process  to the input of the another.</p>
<p>In this mechanism limitd facilities are available.Here should be a server program one client shoud be a send request and the other server would find the client to process the request to server after it invokes the new client so as to process the request.There should be a new client then send a result back to the server,which after it sends data forward to the requesting client.In this process we must use the low level these are file descriptor[fd] so read and write call to access the data rather than fread and fwrite.</p>
<p>In IPC here can be use two methods in pipes:</p>
<p>&gt;&gt;Fork<br />
&gt;&gt;Execl</p>
<p>FORK:It is a function fork()which is used to generate the process and it is used in inter process communication as ret=fork().When we get fork then fork is made two process named “parent id” and &#8216;child id&#8217; which has same address.</p>
<p>EXECL:Execl() is used to invoke the pipe program through which server will get the client.the argument to execl are:</p>
<p>&gt;&gt;The program to invoke<br />
&gt;&gt;argv[0],which takes the program name<br />
&gt;&gt;aggv[1],which contains the file discriptor number we want the program to read from<br />
&gt;&gt;(char *)0,which terminates the parameters.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/11/ipc-mechanism-using-pipes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
