From: Dan Williams <dan.j.williams@intel.com>
To: <alison.schofield@intel.com>, Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>,
Dmytro Adamenko <dmytro.adamenko@intel.com>,
Jason Gunthorpe <jgg@nvidia.com>, Christoph Hellwig <hch@lst.de>
Subject: RE: [PATCH] kernel/resource: Increment by align value in get_free_mem_region()
Date: Mon, 4 Dec 2023 17:17:14 -0800 [thread overview]
Message-ID: <656e7a1a79047_45e01294bd@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20231113221324.1118092-1-alison.schofield@intel.com>
[ add Jason and Christoph for request_free_mem_region() impact ]
alison.schofield@ wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> Currently get_free_mem_region() searches for available capacity
> in increments equal to the region size being requested. This can
> cause the search to take giant steps through the resource leaving
> needless gaps and missing available space.
The bug addressed by this patch is less likely to bite with
request_free_mem_region() compared to alloc_free_mem_region() since the
former does a descending search through the address space that is
unlikely to collide with an existing allocation.
Patch looks good to me, but I would clarify what a CXL end user would
see, so I'll append the following on applying:
"Specifically 'cxl create-region' fails with ERANGE even though capacity
of the given size and CXL's expected 256M x InterleaveWays can be
satisfied".
> Replace the size increment with an alignment increment so that the
> next possible address is always examined for availability.
>
> Fixes: 14b80582c43e ("resource: Introduce alloc_free_mem_region()")
> Reported-by: Dmytro Adamenko <dmytro.adamenko@intel.com>
> Reported-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> ---
>
> A couple of below the line items:
>
> The MAINTAINERS file and get_maintainers script did not emit a clear
> recipient list for this one. Start with CXL folks and I can expand
> it in a v2 with your help.
For this it is sufficient to Cc the other users of
get_free_mem_region() which I did above.
> I considered, but didn't, change the parameter naming in gfr_continue(),
> gfr_next(). It's a choice as get_free_mem_region() is the only caller.
> Thoughts?
Looks fine to me the @size parameter for those helpers should always be
the step value which is @align from the parent routine.
>
>
> kernel/resource.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/resource.c b/kernel/resource.c
> index 866ef3663a0b..91be1bc50b60 100644
> --- a/kernel/resource.c
> +++ b/kernel/resource.c
> @@ -1844,8 +1844,8 @@ get_free_mem_region(struct device *dev, struct resource *base,
>
> write_lock(&resource_lock);
> for (addr = gfr_start(base, size, align, flags);
> - gfr_continue(base, addr, size, flags);
> - addr = gfr_next(addr, size, flags)) {
> + gfr_continue(base, addr, align, flags);
> + addr = gfr_next(addr, align, flags)) {
> if (__region_intersects(base, addr, size, 0, IORES_DESC_NONE) !=
> REGION_DISJOINT)
> continue;
>
> base-commit: b85ea95d086471afb4ad062012a4d73cd328fa86
> --
> 2.37.3
>
next prev parent reply other threads:[~2023-12-05 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 22:13 [PATCH] kernel/resource: Increment by align value in get_free_mem_region() alison.schofield
2023-11-13 23:45 ` Dave Jiang
2023-12-05 1:17 ` Dan Williams [this message]
2023-12-06 7:30 ` Christoph Hellwig
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=656e7a1a79047_45e01294bd@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=dmytro.adamenko@intel.com \
--cc=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=jgg@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.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