public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Re: [PATCH] lmb: Default to not-LMB_USE_MAX_REGIONS
Date: Tue, 7 Feb 2023 11:49:31 -0500	[thread overview]
Message-ID: <Y+KBG2E99RJPhZID@bill-the-cat> (raw)
In-Reply-To: <20230125230823.1567778-1-trini@konsulko.com>

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

On Wed, Jan 25, 2023 at 06:08:23PM -0500, Tom Rini wrote:

> The LMB code allows for picking a hard limit on the number of regions it
> can know of, or to dynamically allocate these regions. The reason for
> this choice is to allow for the compiler to perform a size optimization
> in the common case. This optimization however, is very small, ranging
> from 196 bytes to 15 bytes saved, or in some cases, being larger. Now
> that we also have more regions covered by LMB (in order to protect
> various parts of our self at run time), the default of 8 is also much
> easier to hit and leads to non-obvious error messages (which imply that
> an area is protected, not that we're out of areas to add to the list).
> 
> Switch to the dynamic use as the default.
> 
> Signed-off-by: Tom Rini <trini@konsulko.com>

Applied to u-boot/master, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-02-07 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 23:08 [PATCH] lmb: Default to not-LMB_USE_MAX_REGIONS Tom Rini
2023-02-07 16:49 ` Tom Rini [this message]
2023-02-08 14:33 ` Philippe Schenker
2023-02-08 14:54   ` Tom Rini
2023-02-08 15:13     ` Philippe Schenker
2023-02-08 15:16       ` Tom Rini
2023-02-23 10:01         ` Patrick DELAUNAY

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=Y+KBG2E99RJPhZID@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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