Re: fs/locks.c BKL removal

Dave Hansen (haveblue@us.ibm.com)
Fri, 10 May 2002 15:13:03 -0700

As Linus pointed out, a semaphore is probably the wrong way to go.
The only things that really needs to be protected are the list
operations themselves.

> No, I really think the code should use a spinlock for the global list, and
> then on a per-lock basis something like a reference count and a blocking
> lock (which might be a semaphore).

-- 
Dave Hansen
haveblue@us.ibm.com


-
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/