summaryrefslogtreecommitdiff
path: root/2005/flow-accounting-ols2005/OLS2005/schopp/schopp-abstract.tex
diff options
context:
space:
mode:
Diffstat (limited to '2005/flow-accounting-ols2005/OLS2005/schopp/schopp-abstract.tex')
-rw-r--r--2005/flow-accounting-ols2005/OLS2005/schopp/schopp-abstract.tex21
1 files changed, 21 insertions, 0 deletions
diff --git a/2005/flow-accounting-ols2005/OLS2005/schopp/schopp-abstract.tex b/2005/flow-accounting-ols2005/OLS2005/schopp/schopp-abstract.tex
new file mode 100644
index 0000000..14f77c3
--- /dev/null
+++ b/2005/flow-accounting-ols2005/OLS2005/schopp/schopp-abstract.tex
@@ -0,0 +1,21 @@
+
+% Registration Hotplug Memory Redux
+% [2]Register/Submit Joel H Schopp (jschopp@austin.ibm.com)
+
+Memory Hotplug is one of the most anticipated features
+in the Linux Kernel. The purpose of memory hotplug is
+memory replacement, dynamic workload management, or
+Capacity on Demand of Partitioned/Virtual machines. In
+this paper we discusses the history of Memory Hotplug
+and the LinuxVM including mistakes made along the way
+and technologies which have already been replaced. We
+also discuss the current state of the art in Memory
+Hotplug including user interfaces, \ident{CONFIG_SPARSEMEM},
+the no bitmap buddy allocator, free area splitting
+within zones, and memory migration on PPC64, x86-64,
+and IA64. Additionally, we give a brief discussion on
+the overlap between Memory Hotplug and other areas
+including memory defragmentation and NUMA memory
+management. Finally, we gaze into the crystal ball to
+the future of Memory Hotplug.
+
personal git repositories of Harald Welte. Your mileage may vary