| Summary: | What is Large Memory System? | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | JINKOO HAN <jhan> |
| Component: | Red_Hat_Enterprise_Linux-Release_Notes-7-en-US | Assignee: | Lenka Špačková <lkuprova> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | RHEL DPM <rhel-docs> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | pbokoc, rhel-docs |
| Target Milestone: | rc | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-01-08 07:04:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
JINKOO HAN
2015-12-28 01:41:16 UTC
Hi, I removed the mention of "large memory size" from the doc text - it wasn't the point of the message, it was just an aside and removing it doesn't change much. FYI, there was no set size that was causing problems - it wasn't like "it was fine with 1 CPU as long as the memory was under 64 GB, above that kdump was always having issues". Using multiple CPUs prevents problems that *could* happen, and generally speeds up the process, depending on some other factors (e.g. target disk write speed). Of course, the more memory you have, the more time you save with the speedup - if adding a 2nd CPU made kdump twice as fast, then you might save 15 seconds on a 2GB RAM system and 1500 seconds on a 200GB RAM system. Hope that clears it up. - Petr I have republished the Release Notes with the fixed description of Bug 1182376: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.2_Release_Notes/technology-preview-kernel.html |