From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Peng Zhang <zhangpeng.00@bytedance.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: small optimizations
Date: Mon, 27 Feb 2023 11:04:22 +0200 [thread overview]
Message-ID: <Y/xyFjdgpYP5rm3z@kernel.org> (raw)
Hi Linus,
The following changes since commit 6d796c50f84ca79f1722bb131799e5a5710c4700:
Linux 6.2-rc6 (2023-01-29 13:59:43 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/memblock-v6.3-rc1
for you to fetch changes up to 2fe03412e2e1be3d5ab37b8351a37c3aec506556:
memblock: Avoid useless checks in memblock_merge_regions(). (2023-01-31 15:51:56 +0200)
----------------------------------------------------------------
memblock: small optimizations
* fix off-by-one in the check whether memblock_add_range() should
reallocate memory to accommodate newly inserted range
* check only for relevant regions in memblock_merge_regions() rather than
swipe over the entire array
----------------------------------------------------------------
Peng Zhang (2):
memblock: Make a boundary tighter in memblock_add_range().
memblock: Avoid useless checks in memblock_merge_regions().
mm/memblock.c | 41 +++++++++++++++++++++++++++--------------
1 file changed, 27 insertions(+), 14 deletions(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2023-02-27 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 9:04 Mike Rapoport [this message]
2023-02-27 18:18 ` [GIT PULL] memblock: small optimizations pr-tracker-bot
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/xyFjdgpYP5rm3z@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=zhangpeng.00@bytedance.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.