From: Con Kolivas <lkml@kolivas.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Rajsekar <rajsekar@cse.iitm.ernet.in>, linux-kernel@vger.kernel.org
Subject: Re: SCHED_BATCH not stopped (swsusp fails)
Date: Tue, 11 Jan 2005 10:18:38 +1100 [thread overview]
Message-ID: <41E30D4E.1070007@kolivas.org> (raw)
In-Reply-To: <20050110223213.GC1343@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
>
>
>>SCHED_BATCH processes dont seem to heed the `stop' request (order?) by
>>swsusp. I run httpd and mysqld (for my wiki page) with SCHED_BATCH (so
>>that I can work on my computer even if the load is very high) but when I
>>try to suspend the system, it tries to stop the tasks and simply returns.
>>Here is the dmesg output (paritial)
>
>
> Aha, so if it mysqld is not running SCHED_BATCH priority, stopping
> mysqld will work ok?
That makes sense.
Sorry, SCHED_BATCH is unique to my tree at the moment so this is my
mistake for not considering it. I'll have to transiently schedule
SCHED_BATCH tasks as SCHED_NORMAL if we are going into swsusp. It's
something I'll have to work on. In the interim, a workaround would be to
convert all httpd threads to SCHED_NORMAL before shutting down in your
scripts somewhere and convert them back after resuming.
Cheers,
Con
P.S. Raj the --cutme-- thing in your email is very annoying for those of
us who reply to up to 300 emails a day (and yes I do know why you do it,
but if you keep doing it people will stop replying directly to you).
next prev parent reply other threads:[~2005-01-10 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 19:16 SCHED_BATCH not stopped (swsusp fails) Rajsekar
2005-01-10 22:32 ` Pavel Machek
2005-01-10 23:18 ` Con Kolivas [this message]
[not found] ` <20050110234456.GC1444@elf.ucw.cz>
[not found] ` <m38y70t7lo.fsf@rajsekar.pc>
[not found] ` <41E3D6B4.2080706@kolivas.org>
2005-01-11 20:23 ` Rajsekar
2005-01-11 22:23 ` Con Kolivas
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=41E30D4E.1070007@kolivas.org \
--to=lkml@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rajsekar@cse.iitm.ernet.in \
/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).