From: Aniruddha Banerjee <aniruddhab@nvidia.com>
To: "levinsasha928@gmail.com" <levinsasha928@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"msb@google.com" <msb@google.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [RFC] hung_task: task white-listing for hung tasks
Date: Thu, 12 May 2016 08:51:58 +0000 [thread overview]
Message-ID: <9a25d3183d2e4c99aa942d6beeb151f4@bgmail102.nvidia.com> (raw)
Hello,
In the current hung_task framework, there is no way to white-list tasks for which a higher hang time out might be acceptable and expected even:
Usecase: I want to keep a low hung_task timeout to catch more tasks which are hung-up. However, certain tasks (like sync, which flushes to a slow eMMC) may have a higher timeout.
Problem: There is no way to implement the aforementioned usecase without increasing the hang task timeout, which will reduce the effictiveness of the hung_task framework.
Solution:
1. Introduce a white-list of tasks that have a much higher timeout.
2. Create a simple sysfs interface with which it might be possible to dynamically add/remove any task in the white-list.
Please let me know what you think about the problem and the proposed solution?
Regards,
Aniruddha
reply other threads:[~2016-05-12 8:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9a25d3183d2e4c99aa942d6beeb151f4@bgmail102.nvidia.com \
--to=aniruddhab@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=msb@google.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