[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <pce236tc76vsafgm4bjwy7vcvmqsonun2mnmotxccetfelj3p5@dyhmt45lnnh3>
Date: Mon, 25 Mar 2024 14:24:20 -0700
From: Davidlohr Bueso <dave@...olabs.net>
To: Ira Weiny <ira.weiny@...el.com>
Cc: Dave Jiang <dave.jiang@...el.com>, Fan Ni <fan.ni@...sung.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>, Navneet Singh <navneet.singh@...el.com>,
Dan Williams <dan.j.williams@...el.com>, Alison Schofield <alison.schofield@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>, linux-btrfs@...r.kernel.org, linux-cxl@...r.kernel.org,
linux-kernel@...r.kernel.org, Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>,
David Sterba <dsterba@...e.com>
Subject: Re: [PATCH 15/26] range: Add range_overlaps()
On Sun, 24 Mar 2024, Ira Weiny wrote:
>Code to support CXL Dynamic Capacity devices will have extent ranges
>which need to be compared for intersection not a subset as is being
>checked in range_contains().
>
>range_overlaps() is defined in btrfs with a different meaning from what
>is required in the standard range code. Dan Williams pointed this out
>in [1]. Adjust the btrfs call according to his suggestion there.
>
>Then add a generic range_overlaps().
Reviewed-by: Davidlohr Bueso <dave@...olabs.net>
Powered by blists - more mailing lists