Date: Thu, 21 Nov 2013 12:18:08 -0800 From: Adrian Chadd <adrian@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Andriy Gapon <avg@freebsd.org> Subject: Re: taskqueue_block Message-ID: <CAJ-VmomHZpJ%2BXQz6rrZp2W9_4=2zJ53=6x3B79qO-gL4Hjc4dA@mail.gmail.com> In-Reply-To: <201311211414.06849.jhb@freebsd.org> References: <5287BDB9.10201@FreeBSD.org> <528B7681.6090806@FreeBSD.org> <CAJ-Vmon5AuBDO8q3uddSnvqBTq71r9vW66DAk9oVpLKUUbX0mA@mail.gmail.com> <201311211414.06849.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 November 2013 11:14, John Baldwin <jhb@freebsd.org> wrote: > On Tuesday, November 19, 2013 10:29:18 pm Adrian Chadd wrote: >> Yes, and lets fix this. :) > > Hmm, is taskqueue_block() always used in context where waiting is safe? I seem to recall that a taskqueue function may wish to block further jobs from running. The trouble is that since it was called from a task queued to that particular taskqueue, it'd hang. Sigh. So yes, some slightly saner semantics would be nice. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomHZpJ%2BXQz6rrZp2W9_4=2zJ53=6x3B79qO-gL4Hjc4dA>