All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: David Hildenbrand <david@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-cxl@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Alistair Popple <apopple@nvidia.com>,
	Bjorn Helgaas <bhelgaas@google.com>, Baoquan He <bhe@redhat.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Alison Schofield <alison.schofield@intel.com>
Subject: Re: [RFC] resource: Avoid unnecessary resource tree walking in __region_intersects()
Date: Fri, 11 Oct 2024 13:51:33 +0300	[thread overview]
Message-ID: <ZwkDNVhg495XmoPV@smile.fi.intel.com> (raw)
In-Reply-To: <87zfnb81pi.fsf@yhuang6-desk2.ccr.corp.intel.com>

On Fri, Oct 11, 2024 at 04:48:25PM +0800, Huang, Ying wrote:
> David Hildenbrand <david@redhat.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



  reply	other threads:[~2024-10-11 10:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  6:55 [RFC] resource: Avoid unnecessary resource tree walking in __region_intersects() Huang Ying
2024-10-10 12:54 ` David Hildenbrand
2024-10-11  1:06   ` Huang, Ying
2024-10-11  8:02     ` David Hildenbrand
2024-10-11  8:48       ` Huang, Ying
2024-10-11 10:51         ` Andy Shevchenko [this message]
2024-10-11 10:49     ` Andy Shevchenko
2024-10-11 10:51       ` David Hildenbrand
2024-10-11 11:15         ` Andy Shevchenko
2024-10-11 11:19           ` Andy Shevchenko
2024-10-11 11:30             ` David Hildenbrand
2024-10-11 13:21               ` Huang, Ying
2024-10-23 21:07       ` Dan Williams
2024-10-24  6:57         ` Andy Shevchenko
2024-10-24 12:30           ` Huang, Ying
2024-10-24 13:01             ` Andy Shevchenko
2024-10-24 21:57               ` Dan Williams
2024-10-25  0:31                 ` Huang, Ying
2024-10-25 13:22                 ` Andy Shevchenko
2024-10-25 15:14                   ` Dan Williams
2024-10-28  2:49                     ` Huang, Ying
2024-10-25  0:34               ` Huang, Ying

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZwkDNVhg495XmoPV@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=alison.schofield@intel.com \
    --cc=apopple@nvidia.com \
    --cc=bhe@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=david@redhat.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.