From: Roland Dreier <rdreier@cisco.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: Is adding requeue_delayed_work() a good idea
Date: Wed, 26 Aug 2009 11:42:36 -0700 [thread overview]
Message-ID: <ada7hwqto0z.fsf@cisco.com> (raw)
In-Reply-To: <20090825093906.GA3020@redhat.com> (Oleg Nesterov's message of "Tue, 25 Aug 2009 11:39:06 +0200")
> OK, in this case I think we have a simple solution,
>
> // like cancel_delayed_work, but uses del_timer().
> // this means, if it returns 0 the timer function may be
> // running and the queueing is in progress. The caller
> // can't rely on flush_workqueue/etc
> static inline int __cancel_delayed_work(struct delayed_work *work)
> {
> int ret;
>
> ret = del_timer(&work->timer);
> if (ret)
> work_clear_pending(&work->work);
> return ret;
> }
>
> Now, you can do
>
> spin_lock_irqsave(&mydata_lock);
> new_timeout = add_item_to_timeout_list();
>
> __cancel_delayed_work(&process_timeout_list_work);
> queue_delayed_work(wq, &process_timeout_list_work, new_timeout);
>
> spin_unlock_irqsave(&mydata_lock);
>
> If queue_delayed_work() fails, this means that WORK_STRUCT_PENDING is set,
> dwork->work is already queued or the queueing is in progress. In both
> cases it will run "soon" as if we just called queue_work(&dwork->work).
This looks like it would work well. If we can get this into 2.6.32 then
I will drop my patch and switch to this approach instead.
> But this assumes nobody else does queue_delayed_work(dwork, HUGE_DELAY) in
> parallel, otherwise we can lose the race and another caller can setup
> HUGE_DELAY timeout.
In my case this is fine -- all uses of queue_delayed_work() are
synchronized with the same lock. So any place that tries to shorten the
timeout will succeed.
> In particular, if process_timeout_list_work->func() itself uses
> queue_delay_work() to re-arm itself we can race. Bu t I think it is always
> possible to do something to synchronize with work->func, for example
> work->func() can re-arm itself _before_ it scans timeout_list (under the
> same lock). This way, if re-queue code above fails because work->func()
> wins, work->func() must see the new additions to timeout_list.
In my case, work function does do queue_delayed_work(), but with the
same lock as everyone else held. So there should be no race.
Thanks,
Roland
next prev parent reply other threads:[~2009-08-26 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 21:51 Roland Dreier
2009-08-21 11:55 ` Oleg Nesterov
2009-08-21 21:53 ` Roland Dreier
2009-08-22 10:35 ` Stefan Richter
2009-08-24 18:01 ` Oleg Nesterov
2009-08-24 21:11 ` Roland Dreier
2009-08-25 9:39 ` Oleg Nesterov
2009-08-26 18:42 ` Roland Dreier [this message]
2009-08-28 17:59 ` [PATCH 0/1] introduce __cancel_delayed_work() Oleg Nesterov
2009-08-28 18:00 ` [PATCH 1/1] " Oleg Nesterov
2009-09-01 16:09 ` Roland Dreier
2009-09-01 16:40 ` Dmitry Torokhov
2009-09-01 22:29 ` Andrew Morton
2009-09-01 0:44 ` Is adding requeue_delayed_work() a good idea Dmitry Torokhov
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=ada7hwqto0z.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
/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
Powered by JetHome