[haiku-gsoc] Re: [HCD]: Bfs bug #1
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-gsoc@xxxxxxxxxxxxx
- Date: Sat, 21 Jun 2008 21:27:37 +0200
On 2008-06-21 at 21:15:02 [+0200], Rene Gollent <anevilyak@xxxxxxxxx> wrote:
> On Sat, Jun 21, 2008 at 2:11 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> > Yep, the "sem" debugger command shows which thread has acquired the
> > semaphore
> > last with what count. It also shows who released it last. The acquired
> > count
> > is negated, if the thread already released the semaphore afterwards. I.e.
> > according to your screenshot, the thread has last acquired the semaphore
> > (and
> > not released it since) and now tries to acquire it again. Judging from the
> > sources this could be OK though, since the thread is kind of a consumer
> > thread.
> >
>
> I must have overlooked that....so it's basically using a semaphore as
> a substitute for a condition variable?
I haven't looked that closely, but scsi_service_threadproc() seems to imply
as much. It seems to wait for notifications and process them.
CU, Ingo
Other related posts:
