From: "Huang, Ying" <ying.huang@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-cxl@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Alistair Popple <apopple@nvidia.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>, Baoquan He <bhe@redhat.com>
Subject: Re: [PATCH] Resource: fix region_intersects() for CXL memory
Date: Mon, 02 Sep 2024 10:07:52 +0800 [thread overview]
Message-ID: <87r0a2g64n.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <66c69470ae357_7605294ab@dwillia2-mobl3.amr.corp.intel.com.notmuch> (Dan Williams's message of "Wed, 21 Aug 2024 18:29:20 -0700")
Dan Williams <dan.j.williams@intel.com> writes:
> Huang, Ying wrote:
>> Dan Williams <dan.j.williams@intel.com> writes:
>> > Huang Ying wrote:
> [..]
>> >> kernel/resource.c | 44 +++++++++++++++++++++++++++++++++++++-------
>> >> 1 file changed, 37 insertions(+), 7 deletions(-)
>> >>
>> >> diff --git a/kernel/resource.c b/kernel/resource.c
>> >> index 14777afb0a99..c97a5add9394 100644
>> >> --- a/kernel/resource.c
>> >> +++ b/kernel/resource.c
> [..]
[snip]
>
>> However, I admit that the original code is hard to be understood,
>> whether is something like below better?
>
> I like that this proposal defers incrementing @other rather than
> decrement after the fact.
>
>>
>> for (p = parent->child; p ; p = p->sibling) {
>> if (!resource_overlaps(p, &res))
>> continue;
>> is_type = (((p->flags & flags) == flags) &&
>> ((desc == IORES_DESC_NONE) || (desc == p->desc)));
>> if (is_type) {
>> type++;
>> continue;
>> }
>> /*
>> * Continue to search in descendant resources. Unless
>> * the matched descendant resources cover the whole
>> * overlapped range, increase 'other', because it
>> * overlaps with 'p' at least.
>> */
>> covered = false;
>
> I would call @covered, @single_descendant. Since @covered is ambiguous.
Sorry, I don't understand why this is called @single_descendant. It's
possible that the checked region is overlapped with 2 descendants, and
the result is REGION_INTERSECTS. For example,
490000000-52fffffff : CXL Window 0
490000000-50fffffff : region0
490000000-50fffffff : dax0.0
490000000-50fffffff : System RAM (kmem)
510000000-52fffffff : region1
510000000-52fffffff : dax0.1
510000000-52fffffff : System RAM (kmem)
region_intersects(, 0x50ffff000, 2 * PAGE_SIZE, IORESOURCE_SYSTEM_RAM,
IORES_DESC_NONE) => REGION_INTERSECTS
>> ostart = max(res.start, p->start);
>> oend = min(res.end, p->end);
>> for_each_resource(p, dp, false) {
>> if (!resource_overlaps(dp, &res))
>> continue;
>> is_type = (((dp->flags & flags) == flags) &&
>> ((desc == IORES_DESC_NONE) ||
>> (desc == dp->desc)));
>> if (is_type) {
>> type++;
>> if (dp->start > ostart)
>
> ...this should have a comment:
>
> /* partial descendant overlap indicates overlap with a descendant hole */
Yes. Some comments should help.
>> break;
>> if (dp->end >= oend) {
>> covered = true;
>> break;
>
> ...then per above this because easier to read as:
>
> single_descendant = true;
>
>> }
>> ostart = dp->end + 1;
>> }
>> }
>> if (!covered)
>> other++;
>> }
>>
[snip]
--
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2024-09-02 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 2:07 Huang Ying
2024-08-16 4:53 ` Andrew Morton
2024-08-16 5:07 ` Dan Williams
2024-08-16 8:57 ` David Hildenbrand
2024-08-16 5:01 ` Dan Williams
2024-08-16 7:43 ` Huang, Ying
2024-08-22 1:29 ` Dan Williams
2024-09-02 2:07 ` Huang, Ying [this message]
2024-09-02 11:56 ` Andy Shevchenko
2024-09-03 0:43 ` 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=87r0a2g64n.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.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=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vishal.l.verma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox