Re: [PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-04 Thread Davidlohr Bueso
On Fri, 04 Oct 2019, Matthew Wilcox wrote: On Fri, Oct 04, 2019 at 06:15:11AM -0700, Michel Lespinasse wrote: My take is that this (Davidlohr's) patch series does not necessarily need to be applied all at once - we could get the first change in (adding the interval_tree_gen.h header), and

Re: [PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-04 Thread Jason Gunthorpe
On Fri, Oct 04, 2019 at 06:15:11AM -0700, Michel Lespinasse wrote: > Hi Jason, > > On Thu, Oct 3, 2019 at 5:26 PM Jason Gunthorpe wrote: > > Hurm, this is not entirely accurate. Most users do actually want > > overlapping and multiple ranges. I just studied this extensively: > > (Just curious,

Re: [PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-04 Thread Matthew Wilcox
On Fri, Oct 04, 2019 at 06:15:11AM -0700, Michel Lespinasse wrote: > My take is that this (Davidlohr's) patch series does not necessarily > need to be applied all at once - we could get the first change in > (adding the interval_tree_gen.h header), and convert the first few > users, without

Re: [PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-04 Thread Michel Lespinasse
Hi Jason, On Thu, Oct 3, 2019 at 5:26 PM Jason Gunthorpe wrote: > Hurm, this is not entirely accurate. Most users do actually want > overlapping and multiple ranges. I just studied this extensively: (Just curious, are you the person we discussed this with after the Maple Tree talk at LPC 2019

Re: [PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-04 Thread Michel Lespinasse
On Thu, Oct 03, 2019 at 01:32:50PM -0700, Matthew Wilcox wrote: > On Thu, Oct 03, 2019 at 01:18:47PM -0700, Davidlohr Bueso wrote: > > It has been discussed[1,2] that almost all users of interval trees would > > better > > be served if the intervals were actually not [a,b], but instead [a, b).

Re: [PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-03 Thread Davidlohr Bueso
On Thu, 03 Oct 2019, Jason Gunthorpe wrote: On Thu, Oct 03, 2019 at 01:18:47PM -0700, Davidlohr Bueso wrote: Hi, It has been discussed[1,2] that almost all users of interval trees would better be served if the intervals were actually not [a,b], but instead [a, b). This series attempts to

Re: [PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-03 Thread Jason Gunthorpe
On Thu, Oct 03, 2019 at 01:18:47PM -0700, Davidlohr Bueso wrote: > Hi, > > It has been discussed[1,2] that almost all users of interval trees would > better > be served if the intervals were actually not [a,b], but instead [a, b). This > series attempts to convert all callers by way of

Re: [PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-03 Thread Davidlohr Bueso
On Thu, 03 Oct 2019, Matthew Wilcox wrote: On Thu, Oct 03, 2019 at 01:18:47PM -0700, Davidlohr Bueso wrote: It has been discussed[1,2] that almost all users of interval trees would better be served if the intervals were actually not [a,b], but instead [a, b). This So how does a user

Re: [PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-03 Thread Matthew Wilcox
On Thu, Oct 03, 2019 at 01:18:47PM -0700, Davidlohr Bueso wrote: > It has been discussed[1,2] that almost all users of interval trees would > better > be served if the intervals were actually not [a,b], but instead [a, b). This So how does a user represent a range from ULONG_MAX to ULONG_MAX

[PATCH -next 00/11] lib/interval-tree: move to half closed intervals

2019-10-03 Thread Davidlohr Bueso
Hi, It has been discussed[1,2] that almost all users of interval trees would better be served if the intervals were actually not [a,b], but instead [a, b). This series attempts to convert all callers by way of transitioning from using "interval_tree_generic.h" to "interval_tree_gen.h". Once all