On Wednesday, July 01, 2015 04:25:10 PM John-Mark Gurney wrote:
Ryan Stone wrote this message on Wed, Jul 01, 2015 at 15:44 -0400:
I'm trying to figure out how a driver is supposed to shut down its
interrupt-handling taskqueue when it detaches. taskqueue(9) recommends
disabling interrupts,
On Tue, Jul 07, 2015 at 07:52:56PM -0400, Ryan Stone wrote:
On Thu, Jul 2, 2015 at 3:08 AM, Konstantin Belousov kostik...@gmail.com
wrote:
Having taskqueue_enqueue() which could silently (?) not enqueue the given
task is huge and IMO risky change to the KPI. If doing it, I think
that
On Thu, Jul 2, 2015 at 3:08 AM, Konstantin Belousov kostik...@gmail.com
wrote:
Having taskqueue_enqueue() which could silently (?) not enqueue the given
task is huge and IMO risky change to the KPI. If doing it, I think
that there should be a new function to enqueue, which is allowed to
On Wed, Jul 01, 2015 at 06:28:49PM -0400, Ryan Stone wrote:
On Wed, Jul 1, 2015 at 5:32 PM, Konstantin Belousov kostik...@gmail.com
wrote:
Do you mean, you want some KPI like
boolean taskqueue_is_draining(struct taskqueue *p);
so that e.g. executed task could see if it is
I'm trying to figure out how a driver is supposed to shut down its
interrupt-handling taskqueue when it detaches. taskqueue(9) recommends
disabling interrupts, draining each task and then freeing the taskqueue.
The problem that I have is the interrupt-handling tasks will sometimes
re-enable
But if you've disabled interrupts why would an interrupt-handling task
even run??
Jack
On Wed, Jul 1, 2015 at 12:44 PM, Ryan Stone ryst...@gmail.com wrote:
I'm trying to figure out how a driver is supposed to shut down its
interrupt-handling taskqueue when it detaches. taskqueue(9)
On Wed, Jul 1, 2015 at 4:58 PM, Jack Vogel jfvo...@gmail.com wrote:
But if you've disabled interrupts why would an interrupt-handling task
even run??
Jack
There's a race. The task could have already have been scheduled by a
previous interrupt and could be running while I am trying to
On Wed, Jul 01, 2015 at 05:09:27PM -0400, Ryan Stone wrote:
On Wed, Jul 1, 2015 at 4:58 PM, Jack Vogel jfvo...@gmail.com wrote:
But if you've disabled interrupts why would an interrupt-handling task
even run??
Jack
There's a race. The task could have already have been scheduled by
Or like, taskqueue_enqueue_if_not_draining() ? :p
On Wed, Jul 1, 2015 at 2:32 PM Konstantin Belousov kostik...@gmail.com
wrote:
On Wed, Jul 01, 2015 at 05:09:27PM -0400, Ryan Stone wrote:
On Wed, Jul 1, 2015 at 4:58 PM, Jack Vogel jfvo...@gmail.com wrote:
But if you've disabled
On Wed, Jul 1, 2015 at 5:32 PM, Konstantin Belousov kostik...@gmail.com
wrote:
Do you mean, you want some KPI like
boolean taskqueue_is_draining(struct taskqueue *p);
so that e.g. executed task could see if it is executing in the
shutdown state ?
I'd prefer a KPI that stops a
Ya, that seems elegant.
Jack
On Wed, Jul 1, 2015 at 3:28 PM, Ryan Stone ryst...@gmail.com wrote:
On Wed, Jul 1, 2015 at 5:32 PM, Konstantin Belousov kostik...@gmail.com
wrote:
Do you mean, you want some KPI like
boolean taskqueue_is_draining(struct taskqueue *p);
so that e.g.
Ryan Stone wrote this message on Wed, Jul 01, 2015 at 15:44 -0400:
I'm trying to figure out how a driver is supposed to shut down its
interrupt-handling taskqueue when it detaches. taskqueue(9) recommends
disabling interrupts, draining each task and then freeing the taskqueue.
The problem
12 matches
Mail list logo