On Wed, Sep 11, 2013 at 06:26:25PM +0100, Al Viro wrote:
> On Wed, Sep 11, 2013 at 12:33:35PM -0400, Waiman Long wrote:
>
> > >Folks, any suggestions on better names? The semantics we are getting is
> >
> > I will welcome any better name suggestion and will incorporate that
> > in the patch.
>
On Wed, Sep 11, 2013 at 02:40:38PM -0400, J. Bruce Fields wrote:
> On Wed, Sep 11, 2013 at 06:26:25PM +0100, Al Viro wrote:
> > On Wed, Sep 11, 2013 at 12:33:35PM -0400, Waiman Long wrote:
> >
> > > >Folks, any suggestions on better names? The semantics we are getting is
> > >
> > > I will welco
On 09/11/2013 01:26 PM, Al Viro wrote:
On Wed, Sep 11, 2013 at 12:33:35PM -0400, Waiman Long wrote:
Folks, any suggestions on better names? The semantics we are getting is
I will welcome any better name suggestion and will incorporate that
in the patch.
FWIW, the suggestions I've seen so far
On Wed, Sep 11, 2013 at 12:33:35PM -0400, Waiman Long wrote:
> >Folks, any suggestions on better names? The semantics we are getting is
>
> I will welcome any better name suggestion and will incorporate that
> in the patch.
FWIW, the suggestions I've seen so far had been
seq_exreadlock() [ex f
On 09/11/2013 10:55 AM, Al Viro wrote:
On Wed, Sep 11, 2013 at 10:28:26AM -0400, Waiman Long wrote:
The sequence lock (seqlock) was originally designed for the cases
where the readers do not need to block the writers by making the
readers retry the read operation when the data change.
Since the
On Wed, Sep 11, 2013 at 10:28:26AM -0400, Waiman Long wrote:
> The sequence lock (seqlock) was originally designed for the cases
> where the readers do not need to block the writers by making the
> readers retry the read operation when the data change.
>
> Since then, the use cases have been expan
6 matches
Mail list logo
