From: xpankajbx@gmail.com (Pankaj B)
To: kernelnewbies@lists.kernelnewbies.org
Subject: work_struct not getting scheduled
Date: Thu, 21 Apr 2011 17:44:15 +0530 [thread overview]
Message-ID: <BANLkTikNp7eArwJNWT0EmY3k7j4PFJn2+g@mail.gmail.com> (raw)
Hi,
At my end I was using tasklets to do some handling. But while
doing the handling the handler had to sleep, so I had to switch to
workqueues. I am scheduling a work as follows:
INIT_WORK(&event->work, do_handling_work);
schedule_work(&event->work);
flush_scheduled_work();
But the work never gets scheduled. I have put some printks in the
do_handling_work() function. Creating workqueue and queueing
the work to that workqueue doen't work either. I find this a
very strange problem. Does anybody knows about this?
FYI: my system has heavy IO load when I schedule the work.
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110421/389ae5bb/attachment.html
next reply other threads:[~2011-04-21 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 12:14 Pankaj B [this message]
2011-04-21 15:32 ` work_struct not getting scheduled Michael Blizek
2011-04-23 3:46 ` Pankaj B
2011-04-21 15:59 ` Dave Hylands
2011-04-21 16:42 ` Himanshu Chauhan
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=BANLkTikNp7eArwJNWT0EmY3k7j4PFJn2+g@mail.gmail.com \
--to=xpankajbx@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).