From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org,
Sudarshan Rajagopalan <sudaraja@codeaurora.org>,
David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH 0/1] arm64/sparsemem: reduce SECTION_SIZE_BITS
Date: Thu, 21 Jan 2021 18:26:39 +0000 [thread overview]
Message-ID: <161125239746.2653965.4342337503570976678.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1611206601.git.sudaraja@codeaurora.org>
On Wed, 20 Jan 2021 21:29:12 -0800, Sudarshan Rajagopalan wrote:
> This patch is the follow-up from the discussions in the thread [1].
> Reducing the section size has the merit of reducing wastage of reserved memory
> for vmmemmap mappings for sections with large memory holes. Also with smaller
> section size gives more grunularity and agility for memory hot(un)plugging.
>
> But there are also constraints in reducing SECTION_SIZE_BIT:
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64/sparsemem: reduce SECTION_SIZE_BITS
https://git.kernel.org/arm64/c/f0b13ee23241
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org,
Sudarshan Rajagopalan <sudaraja@codeaurora.org>,
David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org
Cc: Will Deacon <will@kernel.org>, kernel-team@android.com
Subject: Re: [PATCH 0/1] arm64/sparsemem: reduce SECTION_SIZE_BITS
Date: Thu, 21 Jan 2021 18:26:39 +0000 [thread overview]
Message-ID: <161125239746.2653965.4342337503570976678.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1611206601.git.sudaraja@codeaurora.org>
On Wed, 20 Jan 2021 21:29:12 -0800, Sudarshan Rajagopalan wrote:
> This patch is the follow-up from the discussions in the thread [1].
> Reducing the section size has the merit of reducing wastage of reserved memory
> for vmmemmap mappings for sections with large memory holes. Also with smaller
> section size gives more grunularity and agility for memory hot(un)plugging.
>
> But there are also constraints in reducing SECTION_SIZE_BIT:
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64/sparsemem: reduce SECTION_SIZE_BITS
https://git.kernel.org/arm64/c/f0b13ee23241
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-21 18:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 5:29 [PATCH 0/1] arm64/sparsemem: reduce SECTION_SIZE_BITS Sudarshan Rajagopalan
2021-01-21 5:29 ` [PATCH 1/1] " Sudarshan Rajagopalan
2021-01-21 10:08 ` Christoph Lameter
2021-01-21 10:08 ` Christoph Lameter
2021-01-21 10:08 ` Christoph Lameter
2021-01-21 15:54 ` Catalin Marinas
2021-01-21 15:54 ` Catalin Marinas
2021-01-21 13:36 ` Will Deacon
2021-01-21 13:36 ` Will Deacon
2021-01-22 2:58 ` Anshuman Khandual
2021-01-22 2:58 ` Anshuman Khandual
2021-01-21 13:45 ` David Hildenbrand
2021-01-21 13:45 ` David Hildenbrand
2021-01-21 14:16 ` Mike Rapoport
2021-01-21 14:16 ` Mike Rapoport
2021-01-21 16:04 ` David Hildenbrand
2021-01-21 16:04 ` David Hildenbrand
2021-01-21 15:51 ` Catalin Marinas
2021-01-21 15:51 ` Catalin Marinas
2021-01-21 18:26 ` Will Deacon [this message]
2021-01-21 18:26 ` [PATCH 0/1] " Will Deacon
2021-01-29 0:17 ` Pavel Tatashin
2021-01-29 0:17 ` Pavel Tatashin
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=161125239746.2653965.4342337503570976678.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sudaraja@codeaurora.org \
/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.