On 07.08.2013 22:48, Adrian Chadd wrote:
On 7 August 2013 13:08, Scott Long <scott4l...@yahoo.com> wrote:
An even rore relevant difference is that taskqueues have a much stronger
management API. Ithreads can only be scheduled by generating a hardware
interrupt,
can only be drained by calling bus_teardown_intr(), and cannot be paused.
Taskqueues
give you direct access to this control.
It would be really nice if we had a software method to trigger an
ithread to run, like a software interrupt.
It would also be nice to pin taskqueues to CPUs, we can do with
ithreads at the moment.
Both are implemented on top of kernel threads so it's mostly a matter of
nicely integrating and exposing an API for it.
--
Andre
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
