From: "H. Peter Anvin" <hpa@zytor.com>
To: Dave Hansen <dave.hansen@intel.com>,
lizhe.67@bytedance.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org
Cc: lizefan.x@bytedance.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] memmap: introduce cmdline parameter "memmap=nn[KMG]$" without start addr
Date: Thu, 23 Jun 2022 11:22:52 -0700 [thread overview]
Message-ID: <0EA9CBD4-D083-4546-BFAC-9C3A97420E5B@zytor.com> (raw)
In-Reply-To: <de2500c4-fce4-31dc-29bc-aa3007027eb9@intel.com>
On June 23, 2022 7:06:36 AM PDT, Dave Hansen <dave.hansen@intel.com> wrote:
>On 6/22/22 23:24, lizhe.67@bytedance.com wrote:
>> In our scenario, we need reserve or alloc large continous memory like
>> 256M in machine which have different memory specification at just
>> boot phase for a user land process.
>
>Just marking the memory reserved doesn't do any good by itself. There
>must be some *other* kernel code to find this reserved area and make it
>available to userspace.
>
>It seems kinda silly to add this to the kernel without also adding the
>other half of the solution. Plus, we don't really even know what this
>is for. Are there other, better solutions? I certainly can't offer any
>because this changelog did not provide a full picture of the problem
>this solves.
Don't we already have a large contiguous physical memory allocator for this reason (misdesigned hardware?)
next prev parent reply other threads:[~2022-06-23 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 6:24 [RFC] memmap: introduce cmdline parameter "memmap=nn[KMG]$" without start addr lizhe.67
2022-06-23 14:06 ` Dave Hansen
2022-06-23 18:22 ` H. Peter Anvin [this message]
2022-06-28 12:34 ` lizhe.67
2022-06-28 12:30 ` lizhe.67
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=0EA9CBD4-D083-4546-BFAC-9C3A97420E5B@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=lizhe.67@bytedance.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).