public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Momchil Velikov <velco@fadata.bg>
To: Mathijs Mohlmann <mathijs@webflex.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix loop with disabled tasklets
Date: 12 Nov 2001 11:41:05 +0200	[thread overview]
Message-ID: <87d72ojphq.fsf@fadata.bg> (raw)
In-Reply-To: <XFMail.20011112101120.mathijs@webflex.nl>
In-Reply-To: <XFMail.20011112101120.mathijs@webflex.nl>

>>>>> "Mathijs" == Mathijs Mohlmann <mathijs@webflex.nl> writes:

Mathijs> On 12-Nov-2001 Momchil Velikov wrote:
>> In this patch, the first thing is to deschedule the tasklet. So,
>> the changes to interrupt.h are needed in order to put back the
>> tasklet in the queue.
Mathijs> I know, but Andrea suggested not to allow scheduling of
Mathijs> disabled tasklets Also, enableing the tasklet will result in

Disabled tasklets are not scheduled by enable_tasklet (). A disabled
tasklet may temporarily appear in the queue, but nevertheless
tasklet_action will remove it. It seems gross to traverse the list in
order to remove a tasklet at the first disable.

Mathijs> a scheduled tasklet, regardless whether it was
Mathijs> scheduled.

Hmm, if it isn't scheduled, there is not much sense in disabling it at
all.

Mathijs> Plus, we are not sure if it is scheduled on the
Mathijs> same cpu that did the tasklet_schedule (but i might be the
Mathijs> only one who cares about this ;)

Mathijs> thisone we should add some comments to interrupt.h warning
Mathijs> about deadlocks etc.
>> What deadlocks ? ;)
Mathijs> well, loops. Dont use tasklet_kill on disabled tasklet or on
Mathijs> not scheduled tasklets.

Hmm, if TASKLET_STATE_SCHED is not set tasklet_kill will not deadlock.
And tasklet_kill yields (?). Doesn't that mean that tasklet_action
will be called eventually ?

Regards,
-velco




  reply	other threads:[~2001-11-12  9:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11 15:56 [PATCH] fix loop with disabled tasklets Momchil Velikov
2001-11-12  7:46 ` Mathijs Mohlmann
2001-11-12  8:00   ` David S. Miller
2001-11-12  8:07   ` Momchil Velikov
2001-11-12  9:11     ` Mathijs Mohlmann
2001-11-12  9:41       ` Momchil Velikov [this message]
2001-11-12  9:54         ` Mathijs Mohlmann
  -- strict thread matches above, loose matches on Subject: below --
2001-11-12 15:33 Petr Vandrovec
2001-11-12 14:48 ` Andrea Arcangeli
2001-11-10 12:21 Mathijs Mohlmann
2001-11-10 13:37 ` David S. Miller
2001-11-10 15:03   ` Andrea Arcangeli
2001-11-10 15:29     ` Mathijs Mohlmann
2001-11-10 16:02       ` Alan Cox
2001-11-10 16:37       ` Andrea Arcangeli
2001-11-12  1:11         ` Andrea Arcangeli
2001-11-12  7:42           ` Mathijs Mohlmann
2001-11-12  7:59             ` David S. Miller
2001-11-12 14:03               ` Andrea Arcangeli
2001-11-12 13:57             ` Andrea Arcangeli
2001-11-12  8:03           ` David S. Miller
2001-11-12 14:04             ` Andrea Arcangeli
2001-11-12 14:20               ` Andrea Arcangeli
2001-11-12 17:10                 ` Thorsten Kukuk
2001-11-12 19:03                 ` Mathijs Mohlmann
2001-11-11  2:32     ` Mathijs Mohlmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d72ojphq.fsf@fadata.bg \
    --to=velco@fadata.bg \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathijs@webflex.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox