[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZwkDNVhg495XmoPV@smile.fi.intel.com>
Date: Fri, 11 Oct 2024 13:51:33 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: "Huang, Ying" <ying.huang@...el.com>
Cc: David Hildenbrand <david@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-cxl@...r.kernel.org,
Dan Williams <dan.j.williams@...el.com>,
Davidlohr Bueso <dave@...olabs.net>,
Jonathan Cameron <jonathan.cameron@...wei.com>,
Alistair Popple <apopple@...dia.com>,
Bjorn Helgaas <bhelgaas@...gle.com>, Baoquan He <bhe@...hat.com>,
Dave Jiang <dave.jiang@...el.com>,
Alison Schofield <alison.schofield@...el.com>
Subject: Re: [RFC] resource: Avoid unnecessary resource tree walking in
__region_intersects()
On Fri, Oct 11, 2024 at 04:48:25PM +0800, Huang, Ying wrote:
> David Hildenbrand <david@...hat.com> writes:
> > On 11.10.24 03:06, Huang, Ying wrote:
...
> > And just I understand what we want to achieve: we want to walk the
> > subtree below "root" and prevent going to root->sibling or
> > root->parent if "root" is not actually the "real root", correct?
> >
> > X
> > |--------|
> > A----D E
> > |
> > B--C
> >
> > So assume we start walking at A, we want to evaluate A,B,C but not D,E,X.
> >
> > Does that sum up what we want to achieve?
>
> Yes.
Can this explanation be added to the commit message of the next version of
the patch?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists