linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Abu M. Muttalib" <abum@aftek.com>
To: linux-arm-kernel@lists.arm.linux.org.uk, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: FW: significance of process "events/0"
Date: Fri, 9 Jun 2006 20:45:23 +0530	[thread overview]
Message-ID: <BKEKJNIHLJDCFGDBOHGMIEKNCOAA.abum@aftek.com> (raw)

Hi Abu,

Oops, I forgot to CC the list. That's done now.
I suggest you to resend your reply to the list...

Hope someone has a clue...

    :-)

    Michael.
> Hi Mick,
>
> Thats exactly I want to know. My target after this causes an OOM.
>
> ~Abu.
>
> -----Original Message-----
> From: Michael Opdenacker [mailto:michael-lists@free-electrons.com]
> Sent: Friday, June 09, 2006 7:46 PM
> To: Abu M. Muttalib
> Subject: Re: significance of process "events/0"
>
>
> Hi Abu,
>   
>> While running few of the application on target board, running kernel
>>     
> 2.6.13
>   
>> compiled for ARM architecture, I get the following ps listings:
>>
>>   PID  Uid     VmSize Stat Command
>>     1 yoku        528 S   init [3]
>>     2 yoku            SWN [ksoftirqd/0]
>>     3 yoku            SW< [events/0]
>>     4 yoku            SW< [khelper]
>>     5 yoku            SW< [kthread]
>>    18 yoku            SW< [kblockd/0]
>>    43 yoku            SW  [pdflush]
>>    44 yoku            SW  [pdflush]
>>    46 yoku            SW< [aio/0]
>>    45 yoku            SW  [kswapd0]
>>   634 yoku            SW  [mtdblockd]
>>   664 yoku            SWN [jffs2_gcd_mtd1]
>>   773 yoku            SW  [affixd]
>>   800 yoku        540 S   disc_mgr
>>   807 yoku        764 S   btsrv --managekey --nomanagepin
>>   808 yoku        424 S   BT_ActivityMgr
>>   809 yoku        256 S   /root/pwr_key_monitor
>>   839 yoku        840 S   btsdpd -d
>>   863 yoku       1316 S   /bin/sh
>>   879 yoku       1416 S   /root/Angelia
>>   889 yoku       1416 S   /root/Angelia
>>   890 yoku       1416 S   /root/Angelia
>>   891 yoku       1416 S   /root/Angelia
>>   898 yoku       1416 S   /root/Angelia
>>   899 yoku       1416 S   /root/Angelia
>>   900 yoku       1416 S   /root/Angelia
>>   901 yoku       1416 S   /root/Angelia
>>   902 yoku       1416 S < /root/Angelia
>>  1101 yoku            Z < [events/0]
>>  1103 yoku            Z < [events/0]
>>  1178 yoku            Z < [events/0]
>>  1180 yoku            Z < [events/0]
>>  1255 yoku            Z < [events/0]
>>  1257 yoku            Z < [events/0]
>>  1332 yoku            Z < [events/0]
>>  1334 yoku            Z < [events/0]
>>  1411 yoku            Z < [events/0]
>>  1413 yoku            Z < [events/0]
>>  1488 yoku            Z < [events/0]
>>  1490 yoku            Z < [events/0]
>>  1565 yoku            Z < [events/0]
>>  1567 yoku            Z < [events/0]
>>  1642 yoku            Z < [events/0]
>>  1644 yoku            Z < [events/0]
>>  1719 yoku            Z < [events/0]
>>  1721 yoku            Z < [events/0]
>>  1796 yoku            Z < [events/0]
>>  1798 yoku            Z < [events/0]
>>  1873 yoku            Z < [events/0]
>>  1875 yoku            Z < [events/0]
>>  1950 yoku            Z < [events/0]
>>  1952 yoku            Z < [events/0]
>>  2027 yoku            Z < [events/0]
>>  2029 yoku            Z < [events/0]
>>  2104 yoku            Z < [events/0]
>>  2106 yoku            Z < [events/0]
>>  2181 yoku            Z < [events/0]
>>  2183 yoku            Z < [events/0]
>>  2258 yoku            Z < [events/0]
>>  2260 yoku            Z < [events/0]
>>  2337 yoku            Z < [events/0]
>>  2339 yoku            Z < [events/0]
>>
>> I fail to understand what is the relevance of process "events/0"?
>>
>>     
> [events/n] is a kernel thread implementing the default work queue on CPU
> #n , which kernel code can use to run code in process context. See
> http://www.linuxjournal.com/article/6916 for more details.
>
> I just wonder why ps shows many such [events/0]  processes (in Zombie
> state), instead of just one (like on my GNU/Linux PC, for example)...
>
> Cheers,
>
>     Michael.
>
> --
> Michael Opdenacker, Free Electrons
> Free Embedded Linux Training Materials
> on http://free-electrons.com/training
> (More than 1000 pages!)
>
>
>
>   


-- 
Michael Opdenacker, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training
(More than 1000 pages!)


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

                 reply	other threads:[~2006-06-09 15:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BKEKJNIHLJDCFGDBOHGMIEKNCOAA.abum@aftek.com \
    --to=abum@aftek.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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