<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>Comments on: IPC</title>
	<atom:link href="https://www.emblogic.com/blog/06/ipc-2/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.emblogic.com/blog/06/ipc-2/</link>
	<description>Embedded System and ARM Training</description>
	<lastBuildDate>Mon, 07 Oct 2013 04:00:03 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.1</generator>
	<item>
		<title>By: Manoj</title>
		<link>https://www.emblogic.com/blog/06/ipc-2/#comment-825</link>
		<dc:creator><![CDATA[Manoj]]></dc:creator>
		<pubDate>Thu, 21 Jun 2012 03:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://emblogic.org/blog/?p=3400#comment-825</guid>
		<description><![CDATA[Ma&#039;m,

Block on read/write is the state where process is in block state.
Waiting state and block states are differnet with respect to the CPU allocation. 
.
.
A waiting process is waiting for the context switch, where it will get the CPU after a certain time, but a blocked process will not get the CPU untill and unless an particular event occures.
.
.
Eventes can be I/O commands..
.
.

In systems that support virtual memory, a waiting process may be swapped out, that is removed from main memory and placed in virtual memory by the mid-term scheduler. From here the process may be swapped back into the waiting state..
.
.
same case is applied on blocked process also.

thanks]]></description>
		<content:encoded><![CDATA[<p>Ma&#8217;m,</p>
<p>Block on read/write is the state where process is in block state.<br />
Waiting state and block states are differnet with respect to the CPU allocation.<br />
.<br />
.<br />
A waiting process is waiting for the context switch, where it will get the CPU after a certain time, but a blocked process will not get the CPU untill and unless an particular event occures.<br />
.<br />
.<br />
Eventes can be I/O commands..<br />
.<br />
.</p>
<p>In systems that support virtual memory, a waiting process may be swapped out, that is removed from main memory and placed in virtual memory by the mid-term scheduler. From here the process may be swapped back into the waiting state..<br />
.<br />
.<br />
same case is applied on blocked process also.</p>
<p>thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>
