From: Don Zickus <dzickus@redhat.com>
To: peterz@redhat.com, eranian@google.com, fweisbec@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: x86, perf, pmu: make reserve_ds_buffers() allocate memory dynamically
Date: Fri, 24 Jun 2011 12:01:43 -0400 [thread overview]
Message-ID: <20110624160143.GA29969@redhat.com> (raw)
Hi guys,
Some kdump folks noticed that on large machines (say 80 cpu threads), the
kernel reserved a good chunk of memory in the kdump kernel with the call
to reserve_ds_buffers(). About 64k per cpu.
Normally the kdump kernel boots with maxcpus=1 to limit the amount of
processing and memory usage it needs. However, with reserve_ds_buffers()
it seems to allocate a giant chunk of memory due to its use of
for_each_possible_cpu().
I was wondering if it was possible to move some of that allocation to the
cpu_prepare/cpu_starting routines and allocate during a cpu hotplug event.
I am not sure if some of this allocation is on a per cpu basis (which
includes multiple cores) or if there is some sort of other restriction
that required the code to be statically allocated at boot time.
Thanks,
Don
next reply other threads:[~2011-06-24 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 16:01 Don Zickus [this message]
2011-06-28 10:38 ` x86, perf, pmu: make reserve_ds_buffers() allocate memory dynamically Peter Zijlstra
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=20110624160143.GA29969@redhat.com \
--to=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@redhat.com \
/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