Re: [PATCH v6 5/6] MCS Lock: Restructure the MCS lock defines andlocking code into its own file

From: Ingo Molnar
Date: Thu Sep 26 2013 - 05:37:31 EST



* Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:

> On Thu, Sep 26, 2013 at 08:46:29AM +0200, Ingo Molnar wrote:
> > > +/*
> > > + * MCS lock defines
> > > + *
> > > + * This file contains the main data structure and API definitions of MCS lock.
> >
> > A (very) short blurb about what an MCS lock is would be nice here.
>
> A while back I suggested including a link to something like:
>
> http://www.cise.ufl.edu/tr/DOC/REP-1992-71.pdf
>
> Its a fairly concise write-up of the idea; only 6 pages. The sad part
> about linking to the web is that links tend to go dead after a while.

So what I wanted to see was to add just a few sentences summing up the
concept - so that people blundering into this file in include/linux/ have
an idea what it's all about!

Thanks,

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