Re: [PATCH v2 2/3] mutex: add support for reservation style locks, v2
From: Steven Rostedt
Date: Tue Apr 09 2013 - 18:42:32 EST
On Thu, Apr 04, 2013 at 06:56:58PM +0200, Daniel Vetter wrote:
> I think for starters we need to have a slightly more interesting example:
> 3 threads O, M, Y: O has the oldest ww_age/ticket, Y the youngest, M
> is in between.
> 2 ww_mutexes: A, B
> Y has already acquired ww_mutex A, M has already acquired ww_mutex B.
Now I probably missed it in the thread somewhere, but what makes task O
the oldest and Y the youngest? Is it the actual time from when the task
was created? What about setting an age as soon as it starts the process
of grabbing one of these locks? And it keeps the age until it
successfully grabs and releases all the locks again. It wont reset if it
had to drop the locks and start over.
Or am I totally not understanding what's going on here? Which could also
be the case ;-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/