[Top] [All Lists]

(no subject)

To: "" <>, linux-mips <>
Subject: (no subject)
From: veerasena reddy <>
Date: Fri, 1 Feb 2008 23:44:47 +0530 (IST)
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;; h=X-YMail-OSG:Received:X-Mailer:Date:From:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=XXiF+t2gJVn66gjvUZ1OjONzOY2n8+66gUGFHpAuU5bdh6XgkCPE42Pzmyn+Rf9Lri0eULQgbzk+mcPIOjvt73HnsS04Q4ELhxXxoubGdKgrH7HEiF/aqdYl+tY+Z7gQavbBEVgOT+q4Mfjyt9qaKk3vDiILkI7smyeRIozfxhE=;
Original-recipient: rfc822;

I have a requirement where i need to execute a user process even when the 
kernel is utilizing 100% of CPU time.

Actual scenario is as below:
I have a device on my board. this device keeps generating regular (for every 
2secs) messages for a user process. the user process has to poll on the device 
for any message is there to read and get the message from the device. once the 
user process reads the message it will be removed in device and uses for 
further/subsequent messages.

I have a test case where i need to send so much traffic through my board such 
that the kernel will be utilizing 100% CPU time to process this data. At this 
time (when CPU is 100% utilized) the user space process is not getting 
scheduled even after a long duration (say 10 minutes to 45 minutes). Mean time 
the message buffer in the device is filled up and the device halts (aka 
controlled crash; the device firmware has been designed like this) as there is 
no more memory on the device.
To avoid this scenario of device's message queue getting filled up because of 
the user space process not reading them, could you please anyone suggest some 
technique for getting my user space process scheduled even when there is very 
heavy traffic as described above.

In simple, i can put my requirement like this:
    Is there any way i can get a user space process get scheduled in the above 
condition (kernel occupying 100% of CPU due to heavy traffic)

Thanks in Advance.


      Now you can chat without downloading messenger. Go to

<Prev in Thread] Current Thread [Next in Thread>