Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1618185

Re: [PATCH 2/6] locking: Introduce range reader/writer lock

From Davidlohr Bueso <dave@stgolabs.net>
Newsgroups linux.kernel
Subject Re: [PATCH 2/6] locking: Introduce range reader/writer lock
Date 2017-04-06 19:00 +0200
Message-ID <ttiVj-3pQ-1@gated-at.bofh.it> (permalink)
References <ttbh9-6aP-61@gated-at.bofh.it> <ttbqO-6ei-37@gated-at.bofh.it> <ttbAx-6xa-79@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, 06 Apr 2017, Laurent Dufour wrote:

>How is 'seqnum' wrapping handled here ?
>I'd rather see something like time_before() here, isn't it ?

Its a 64bit counter, no overflows.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v2 -tip 0/6] locking: Introduce range reader/writer lock Davidlohr Bueso <dave@stgolabs.net> - 2017-04-06 11:00 +0200
  [PATCH 6/6] staging/lustre: Use generic range rwlock Davidlohr Bueso <dave@stgolabs.net> - 2017-04-06 11:00 +0200
    Re: [PATCH 6/6] staging/lustre: Use generic range rwlock "Dilger, Andreas" <andreas.dilger@intel.com> - 2017-04-07 12:10 +0200
  [PATCH 4/6] locking/locktorture: Fix num reader/writer corner cases Davidlohr Bueso <dave@stgolabs.net> - 2017-04-06 11:00 +0200
  [PATCH 1/6] interval-tree: Build unconditionally Davidlohr Bueso <dave@stgolabs.net> - 2017-04-06 11:00 +0200
  [PATCH 2/6] locking: Introduce range reader/writer lock Davidlohr Bueso <dave@stgolabs.net> - 2017-04-06 11:00 +0200
    Re: [PATCH 2/6] locking: Introduce range reader/writer lock Laurent Dufour <ldufour@linux.vnet.ibm.com> - 2017-04-06 11:10 +0200
      Re: [PATCH 2/6] locking: Introduce range reader/writer lock Davidlohr Bueso <dave@stgolabs.net> - 2017-04-06 19:00 +0200
    Re: [PATCH 2/6] locking: Introduce range reader/writer lock Peter Zijlstra <peterz@infradead.org> - 2017-04-06 12:30 +0200

csiph-web