From: Joerg Roedel <joro@8bytes.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Borislav Petkov <bp@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Kosina <jkosina@suse.cz>, Vivek Goyal <vgoyal@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel low memory reserving failed
Date: Wed, 22 Jul 2015 12:11:33 +0200 [thread overview]
Message-ID: <20150722101133.GH10969@8bytes.org> (raw)
In-Reply-To: <CAE9FiQUYxiR4DnKysp0DQpM-5cbkMF5jNG=bWCYE_FEMPR=how@mail.gmail.com>
On Tue, Jul 21, 2015 at 12:22:53PM -0700, Yinghai Lu wrote:
> On Tue, Jul 21, 2015 at 1:58 AM, Baoquan He <bhe@redhat.com> wrote:
>
> > Maybe system which don't need low memory is rare, only for testing?
>
> No, it is not rare.
>
> All recent intel based systems with iommu support does not need low.
All Intel-IOMMU systems have the iommu disabled by default (at least
that is the default in most distros). So low memory is definitly needed
by those systems too.
> that reserve 256M low always. and those 256M get wasted.
>
> That commit should only be used to workaround some systems that
> have partial iommu support.
We currently lack the infrastructure for that, but I am happy to review
patches. How about letting subsystems announce their need for low
crash-kernel memory and allocate based on that?
The subsystems (like iommu or swiotlb code, for example) could even
announce how much memory they need and we base our allocation on that.
Joerg
next prev parent reply other threads:[~2015-07-22 10:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 11:07 [PATCH] Do not reserve crashkernel high memory if crashkernel low memory reserving failed Baoquan He
2015-07-19 13:40 ` Borislav Petkov
2015-07-19 14:23 ` Baoquan He
2015-07-19 14:53 ` [PATCH v2] " Baoquan He
2015-07-21 7:31 ` Dave Young
2015-07-21 7:38 ` Ingo Molnar
2015-07-21 8:19 ` Dave Young
2015-07-22 1:13 ` Baoquan He
2015-07-27 14:45 ` Joerg Roedel
2015-07-21 7:50 ` Baoquan He
2015-07-21 8:23 ` Dave Young
2015-07-21 8:58 ` Baoquan He
2015-07-21 19:22 ` Yinghai Lu
2015-07-22 0:59 ` Baoquan He
2015-07-22 23:47 ` Yinghai Lu
2015-07-28 0:52 ` Baoquan He
2015-07-28 2:45 ` Yinghai Lu
2015-07-28 9:19 ` Baoquan He
2015-07-22 4:47 ` Minfei Huang
2015-07-22 23:44 ` Yinghai Lu
2015-07-22 10:11 ` Joerg Roedel [this message]
2015-07-22 23:41 ` Yinghai Lu
2015-07-27 14:03 ` Joerg Roedel
2015-07-27 18:31 ` Yinghai Lu
2015-07-27 23:32 ` Baoquan He
2015-07-27 14:41 ` Joerg Roedel
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=20150722101133.GH10969@8bytes.org \
--to=joro@8bytes.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@suse.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=yinghai@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 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.