[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZYWQYNlYynPRdecK@smile.fi.intel.com>
Date: Fri, 22 Dec 2023 15:34:24 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: linux-pci@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Rob Herring <robh@...nel.org>,
Krzysztof Wilczyński <kw@...ux.com>,
Igor Mammedov <imammedo@...hat.com>, Lukas Wunner <lukas@...ner.de>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
"Rafael J . Wysocki" <rafael@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/7] resource: Handle simple alignment inside
__find_empty_resource_slot()
On Fri, Dec 22, 2023 at 02:28:59PM +0200, Ilpo Järvinen wrote:
> allocate_resource() accepts alignf callback to perform custom alignment
s/alignf callback/->alignf() callback/
?
> beyond constraint->align. If alignf is NULL, simple_align_resource() is
> used which only returns avail->start (no change).
>
> Using avail->start directly is natural and can be done with a
> conditional in __find_empty_resource_slot() instead which avoids
> unnecessarily using callback. It makes the code inside
> __find_empty_resource_slot() more obvious and removes the need for the
> caller to provide constraint->alignf unnecessarily.
>
> This is preparation for exporting find_empty_resource_slot().
Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
...
> if (avail.start >= tmp.start) {
> alloc.flags = avail.flags;
> - alloc.start = constraint->alignf(constraint->alignf_data, &avail,
> - size, constraint->align);
> + if (alignf) {
> + alloc.start = alignf(constraint->alignf_data,
> + &avail, size,
> + constraint->align);
Maybe one line? It used to be a longer line in the old code.
> + } else {
> + alloc.start = avail.start;
> + }
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists