From: christophe barbe <christophe.barbe@lineo.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: uninteruptable sleep (D state => load_avrg++)
Date: Wed, 4 Apr 2001 09:47:08 +0200 [thread overview]
Message-ID: <20010404094708.A4718@pc8.inup.com> (raw)
In-Reply-To: <003501c0bc5c$e26e81c0$5517fea9@local>
In-Reply-To: <003501c0bc5c$e26e81c0$5517fea9@local>; from manfred@colorfullife.com on mar, avr 03, 2001 at 18:40:53 +0200
Sorry if I fork a bit the thread but I'm wondering why the load average is incremented for each D process.
I don't know if the kernel use this information (if yes please let me know).
But some programs like sendmail use this information to sleep when the load is too high (I believe from 12 for sendmail).
It makes sence but in the case of D process, the load average give a bad idea of the load because these process don't use CPU.
I use GFS to share a filesystem on several nodes.
The file locking use real IO and so when you ask for a lock, if the lock is already owned, you fall in a D state.
This differs from what a local filesystem does but IMHO makes sense for a distributed filesytem like GFS.
Christophe
On mar, 03 avr 2001 18:40:53 Manfred Spraul wrote:
> > ps xl:
> > F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
> > 040 1000 1230 1 9 0 24320 4 down_w D ? 0:00
> > /home/data/mozilla/obj/dist/bin/mozi
> >
> down_w
>
> Perhaps down_write_failed()? 2.4.3 converted the mmap semaphore to a
> rw-sem.
> Did you compile sysrq into your kernel? Then enable it with
>
> #echo 1 > /proc/sys/kernel/sysrq
> and press <Alt>+<SysRQ>+'t'
>
> It prints the complete back trace, not just one function name
>
> --
> Manfred
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Christophe Barbé
Software Engineer
Lineo High Availability Group
42-46, rue Médéric
92110 Clichy - France
phone (33).1.41.40.02.12
fax (33).1.41.40.02.01
www.lineo.com
next prev parent reply other threads:[~2001-04-04 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 16:40 uninteruptable sleep Manfred Spraul
2001-04-04 7:47 ` christophe barbe [this message]
2001-04-04 11:15 ` uninteruptable sleep (D state => load_avrg++) Alan Cox
2001-04-04 12:13 ` christophe barbe
2001-04-04 12:53 ` Alan Cox
2001-04-04 14:20 ` Paul Jakma
2001-04-04 14:48 ` christophe barbe
2001-04-04 15:05 ` Paul Jakma
2001-04-04 15:15 ` christophe barbe
2001-04-04 22:39 ` Tim Wright
2001-04-04 16:07 ` uninteruptable sleep christophe barbe
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=20010404094708.A4718@pc8.inup.com \
--to=christophe.barbe@lineo.fr \
--cc=linux-kernel@vger.kernel.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