From: Alan <alan@lxorguk.ukuu.org.uk>
To: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Arjan van de Ven <arjan@infradead.org>,
mingo@redhat.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/2] semaphores: add down_interruptible_timeout() and asm-generic/semaphore.h
Date: Tue, 27 Feb 2007 02:18:03 +0000 [thread overview]
Message-ID: <20070227021803.38c8591f@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <200702261654.18005.inaky@linux.intel.com>
> Yeah, I need semaphore. This is a hw register that says when the hw
> is ready to accept a new command. Code that wants to send commands has
> to down the semaphore and then send it. When hw is ready to get a new
> command, it sends and IRQ and the IRQ up()s the semaphore.
So you need a mutex not a semaphore
>
> Now, we don't want to hang on that down() forever if the hw spaces out.
> If we get a timeout, we can try recovery actions (like resetting it,
> for sake of being polite).
Makes sense but you can also do that with mutexes, and its
mutex_interruptible_timeout() you need I suspect ?
Alan
next prev parent reply other threads:[~2007-02-27 1:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 0:13 inaky
2007-02-27 0:13 ` [patch 1/2] semaphores: Add down_interruptible_timeout() inaky
2007-02-27 0:13 ` [patch 2/2] semaphores: all arches use include/asm-generic/semaphore.h inaky
2007-02-27 0:33 ` [patch 0/2] semaphores: add down_interruptible_timeout() and asm-generic/semaphore.h Christoph Hellwig
2007-02-27 0:54 ` Inaky Perez-Gonzalez
2007-02-27 2:18 ` Alan [this message]
2007-02-27 1:57 ` Inaky Perez-Gonzalez
2007-02-27 20:45 ` Ingo Oeser
2007-03-03 1:17 ` Inaky Perez-Gonzalez
2007-02-27 20:24 ` Andrew Morton
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=20070227021803.38c8591f@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=inaky@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®