Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1193204 > unrolled thread
| Started by | Joerg Roedel <joro@8bytes.org> |
|---|---|
| First post | 2015-07-27 16:50 +0200 |
| Last post | 2015-07-27 16:50 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel low memory reserving failed Joerg Roedel <joro@8bytes.org> - 2015-07-27 16:50 +0200
| From | Joerg Roedel <joro@8bytes.org> |
|---|---|
| Date | 2015-07-27 16:50 +0200 |
| Subject | Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel low memory reserving failed |
| Message-ID | <pQRT4-4QW-15@gated-at.bofh.it> |
On Tue, Jul 21, 2015 at 09:38:14AM +0200, Ingo Molnar wrote: > Also, why was this syntax introduced in the first place? Why should the user > care?? > > We should only have a single crashkernel option, to enable it - and everything > else should be figured out by the kernel, automatically. > > Any other sub-options just paper over some fragility elsewhere and make the > feature harder to use, hence more fragile. Hmm, maybe the reason is that old userspace (kdump/kexec tools) can't deal with crashkernel loaded high, so that the default for crashkernel=size allocations was kept to be under 896MB. If that's not an issue we can change the default and get rid of the ,high and ,low syntax. Joerg -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web