You still want to use daemonzie
> - is there no need to call daemonize in the second variant - if yes why?
A task always has a parent, it'll just be a random task that ran the
kernel_thread request - in fact it might be a kernel thread and then
I dont guarantee what will occur. In fact I wouldnt try the tq_schedule one
> - can i do both variants during interupt time (when there is no valid
> current)?
No, but you can create a thread ready in case its needed then wake it from
an IRQ
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/