On 6 December 2010 18:44, Sjoerd <fedora001@xxxxxxxxxx> wrote:
What you are seeing is one kernel thread per CPU. You can general identify kernel threads as opposed to normal user-level processes because the process name is in square brackets; if you use "ps -le" instead you'll also see that they have zero memory.
I don't know why the nouveau and radeon drivers organise themselves this way, but having threads pinned to each CPU (I presume they are pinned, they normally are) allows for some clever cpu cache and locking performance improvements.
It's nothing to do with the number of outputs of the card. You may or may not get one kernel thread per card per cpu.
jch
I have an i7 processor running F14 and I see 8 instances of the radeon driver and only one card in the system:
03:00.0 VGA compatible controller: ATI Technologies Inc RV730XT [Radeon HD 4670]
$ ps -af | grep radeon
root 155 2 0 03:22 ? 00:00:00 [radeon/0]
root 156 2 0 03:22 ? 00:00:00 [radeon/1]
root 157 2 0 03:22 ? 00:00:00 [radeon/2]
root 158 2 0 03:22 ? 00:00:00 [radeon/3]
root 159 2 0 03:22 ? 00:00:00 [radeon/4]
root 160 2 0 03:22 ? 00:00:00 [radeon/5]
root 161 2 0 03:22 ? 00:00:00 [radeon/6]
root 162 2 0 03:22 ? 00:00:00 [radeon/7]
What you are seeing is one kernel thread per CPU. You can general identify kernel threads as opposed to normal user-level processes because the process name is in square brackets; if you use "ps -le" instead you'll also see that they have zero memory.
I don't know why the nouveau and radeon drivers organise themselves this way, but having threads pinned to each CPU (I presume they are pinned, they normally are) allows for some clever cpu cache and locking performance improvements.
It's nothing to do with the number of outputs of the card. You may or may not get one kernel thread per card per cpu.
jch
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
