https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785
--- Comment #5 from John Baldwin j...@freebsd.org ---
Well, cpuset -x forces affinity for the ithread even if the driver did not
request it. I do believe that em does not request specific affinity on its
own.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785
--- Comment #6 from gon...@bsdinfo.com.br ---
So it's not a bug, it's a feature of the driver. Can we close this bug then.
Thanks and best regards
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785
John Baldwin j...@freebsd.org changed:
What|Removed |Added
Status|Needs Triage|Issue Resolved
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785
--- Comment #8 from gon...@bsdinfo.com.br ---
Yes it changes the CPU. With top -PSH you can see it changing CPU.
I did: cpuset -x 264 -l 3
See my top below:
PID USERNAME PRI NICE SIZERES STATE C TIMEWCPU COMMAND
10
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785
--- Comment #9 from John Baldwin j...@freebsd.org ---
Ah, the em0 que thread is a separate helper thread created by the em driver
to service a taskqueue. It is not an interrupt thread so it is not affected by
'cpuset -x'. However, you can
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785
--- Comment #10 from gon...@bsdinfo.com.br ---
Cool Thanks! Works now. :D
Cheers,
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785
John Baldwin j...@freebsd.org changed:
What|Removed |Added
CC||j...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Summary|cpu affinity not working in |[em] cpu
