From: christophe barbe <christophe.barbe@lineo.fr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: uninteruptable sleep (D state => load_avrg++)
Date: Wed, 4 Apr 2001 14:13:49 +0200 [thread overview]
Message-ID: <20010404141349.A6702@pc8.inup.com> (raw)
In-Reply-To: <20010404094708.A4718@pc8.inup.com> <E14klGU-0001kB-00@the-village.bc.nu>
In-Reply-To: <E14klGU-0001kB-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on mer, avr 04, 2001 at 13:15:52 +0200
The sleep should certainly be interruptible and I that's what I said to the GFS guy.
But what the reason to increment the load average for each D process ?
Thanks,
Christophe
On mer, 04 avr 2001 13:15:52 Alan Cox wrote:
> > The file locking use real IO and so when you ask for a lock, if the loc=
> > k is already owned, you fall in a D state.
>
> That seems odd. They should be using interruptible sleeps so you can interrupt
> the task waiting for the lock, surely.
>
> -
> 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 12:10 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 ` uninteruptable sleep (D state => load_avrg++) christophe barbe
2001-04-04 11:15 ` Alan Cox
2001-04-04 12:13 ` christophe barbe [this message]
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=20010404141349.A6702@pc8.inup.com \
--to=christophe.barbe@lineo.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.