From: Ingo Oeser <ioe-lkml@rameria.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: state terminology
Date: Sun, 15 Jan 2006 10:58:48 +0100 [thread overview]
Message-ID: <200601151058.55369.ioe-lkml@rameria.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0601142234280.23423@yvahk01.tjqt.qr>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
Hi Jan,
On Saturday 14 January 2006 22:34, you wrote:
> Is there a specific term (other than "hang") associated with this
> situation? It's not a "dead-lock", because there is no other process
> (anymore) which could potentially up the semaphore.
This is a simple "resource leak" (or "semaphore leak" in this case).
Explanation follows:
The resource semaphore is not usable by anyone anymore
and is still around.
Its pretty much the same as a memory leak. There is no one, who
could free the memory anymore.
The reasons for the resource not being usable anymore is
not significant for a resource leak.
Also insignificant is the fact that the amount of semaphores
are just limited by available memory. If you repeat starting threads
doing the semaphore leak game from your example, you'll run out
of memory and thus out of semaphores. This is another sign of leakage.
Do the above explanations sound ok?
Regards
Ingo Oeser
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-15 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 21:34 Jan Engelhardt
2006-01-15 9:58 ` Ingo Oeser [this message]
2006-01-15 20:00 ` Paul Dickson
2006-01-15 20:55 ` Jan Engelhardt
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=200601151058.55369.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=jengelh@linux01.gwdg.de \
--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
all inboxes | Powered by JetHome®