t creating a new worker but using the generic kernel worker
(kworker) to handle your work. Besides, there is no CPU bound for this work,
which means any CPU is able to run the work.
Dave Tian
dave.jing.t...@gmail.com
On Nov 19, 2014, at 11:21 PM, 户户 <6563...@163.com> wrote:
I'
I'm playing around with work_queue in my VMware workstation. but I hit a
problem that the work is processed by [kworker/3:1] other than my work queue.
static int __init test_init(void)
{
pr_info(" (*) test_init start - pid:%d. cpu:%d\n", current->pid, get_cpu());
int ret = 0;
test_que
