On 8/28/12 3:44 PM, John Baldwin wrote:
On Monday, August 27, 2012 4:47:13 pm Lev Serebryakov wrote:
Hello, John.
You wrote 27 августа 2012 г., 20:26:03:
What fast tasks are performed via this queue? Under network load it
is main consumer of CPU.
JB Certain NIC drivers perform much of
Hello, Andrey.
You wrote 29 августа 2012 г., 11:17:09:
AZ If you have more than one CPU, you can try this patch [1]. It adds
I have only one cput (Geode LX 500 Mhz) without any HT or other
virtual CPUs at all. One core, one thread :)
--
// Black Lion AKA Lev Serebryakov l...@freebsd.org
On Monday, August 27, 2012 4:47:13 pm Lev Serebryakov wrote:
Hello, John.
You wrote 27 августа 2012 г., 20:26:03:
What fast tasks are performed via this queue? Under network load it
is main consumer of CPU.
JB Certain NIC drivers perform much of their interrupt handling in that
thread.
Hello, Lev.
You wrote 27 августа 2012 г., 6:19:57:
I've found (with help of debug printing added to kernel), that swi5
has only one handler Fast task queue (name is too long to be seen in
`top' output, may be, rename it to fast tqueue?)
What fast tasks are performed via this queue? Under
On Monday, August 27, 2012 8:46:46 am Lev Serebryakov wrote:
Hello, Lev.
You wrote 27 августа 2012 г., 6:19:57:
I've found (with help of debug printing added to kernel), that swi5
has only one handler Fast task queue (name is too long to be seen in
`top' output, may be, rename it to fast
Hello, John.
You wrote 27 августа 2012 г., 20:26:03:
What fast tasks are performed via this queue? Under network load it
is main consumer of CPU.
JB Certain NIC drivers perform much of their interrupt handling in that thread.
Yep, I've found, that my if_vr uses it. One more question: does
