On Thu, Aug 09, 2012 at 12:33:17PM -0700, John Stultz wrote:
> On 08/09/2012 06:35 AM, Andrea Righi wrote:
> >On Thu, Aug 09, 2012 at 02:46:37AM -0700, Michel Lespinasse wrote:
> >>On Fri, Jul 27, 2012 at 8:57 PM, John Stultz wrote:
> >>>v5:
> >>>* Drop intervaltree for prio_tree usage per Michel
On 08/09/2012 06:35 AM, Andrea Righi wrote:
On Thu, Aug 09, 2012 at 02:46:37AM -0700, Michel Lespinasse wrote:
On Fri, Jul 27, 2012 at 8:57 PM, John Stultz wrote:
v5:
* Drop intervaltree for prio_tree usage per Michel &
Dmitry's suggestions.
Actually, I believe the ranges you need to track
On 08/09/2012 02:46 AM, Michel Lespinasse wrote:
On Fri, Jul 27, 2012 at 8:57 PM, John Stultz wrote:
v5:
* Drop intervaltree for prio_tree usage per Michel &
Dmitry's suggestions.
Actually, I believe the ranges you need to track are non-overlapping, correct ?
Correct. Any overlapping rang
On Thu, Aug 09, 2012 at 02:46:37AM -0700, Michel Lespinasse wrote:
> On Fri, Jul 27, 2012 at 8:57 PM, John Stultz wrote:
> > v5:
> > * Drop intervaltree for prio_tree usage per Michel &
> > Dmitry's suggestions.
>
> Actually, I believe the ranges you need to track are non-overlapping, correct
On Fri, Jul 27, 2012 at 8:57 PM, John Stultz wrote:
> v5:
> * Drop intervaltree for prio_tree usage per Michel &
> Dmitry's suggestions.
Actually, I believe the ranges you need to track are non-overlapping, correct ?
If that is the case, a simple rbtree, sorted by start-of-range
address, would
This patch provides the volatile range management code
that filesystems can utilize when implementing
FALLOC_FL_MARK_VOLATILE.
It tracks a collection of page ranges against a mapping
stored in an interval-tree. This code handles coalescing
overlapping and adjacent ranges, as well as splitting
rang
6 matches
Mail list logo
