[Solved] Curious processes

[feffer]

Just curious about all these "kworker" and "migration" processes running on my standard gnome-based LMDE.

Code: Select all

$ ps -e | grep kworker
    4 ?        00:00:00 kworker/0:0
   11 ?        00:00:00 kworker/0:1
   18 ?        00:00:00 kworker/3:0
   22 ?        00:00:00 kworker/4:0
   26 ?        00:00:00 kworker/5:0
   30 ?        00:00:00 kworker/6:0
   34 ?        00:00:00 kworker/7:0
   47 ?        00:00:00 kworker/1:1
   48 ?        00:00:00 kworker/2:1
   49 ?        00:00:00 kworker/3:1
   50 ?        00:00:00 kworker/4:1
   51 ?        00:00:00 kworker/5:1
   52 ?        00:00:00 kworker/6:1
   53 ?        00:00:00 kworker/7:1
  236 ?        00:00:00 kworker/0:2
  256 ?        00:00:00 kworker/u:4
  257 ?        00:00:00 kworker/u:5
  333 ?        00:00:00 kworker/1:2
  346 ?        00:00:00 kworker/4:2
  846 ?        00:00:00 kworker/0:3
 3408 ?        00:00:00 kworker/2:2
 3565 ?        00:00:00 kworker/4:3
$ ps -e | grep migration
    6 ?        00:00:00 migration/0
    8 ?        00:00:00 migration/1
   13 ?        00:00:00 migration/2
   17 ?        00:00:00 migration/3
   21 ?        00:00:00 migration/4
   25 ?        00:00:00 migration/5
   29 ?        00:00:00 migration/6
   33 ?        00:00:00 migration/7

[DrHu]

Just curious about all these "kworker" and "migration" processes running on my standard gnome-based LMDE

Possibly that kde, gnome are part of freedesktop.org, and have cross-desktop compatibilities enabled..
http://groups.google.com/group/linux.ke ... 2?lnk=raot

http://groups.google.com/group/linux.de ... abd64597b0
http://ubuntuforums.org/showthread.php?t=1630347
https://answers.launchpad.net/ubuntu/+question/138681
--not that much information this process (kworker..)

http://igurublog.wordpress.com/2011/03/31/
--that might be a little more helpful, however if you stop device activity such as acpi or usb or others which might kill kworker, them you will be creating other problems for yourself. Unless kworker is hanging your system or slowing it significantly, i guess we just have to wait for some answers

[feffer]

OK, thx. Looked over the links. It's not absolutely clear, but you're probably right it has to do with cross-desktop capabilities. It seems like these processes are using CPU and generally not behaving well for some, but in my case, TOP shows they are quiet -- so let sleeping dogs lie.