One - The Linux Kernel Archives

More documents

Recommendations

Info

286 • Linux Symposium 2004 • Volume One [11] For more information on Mandatory Access Control (MAC), see http:// csrc.nist.gov/publications/ nistpubs/800-7/node35.html [12] For more information on Discretionary Access Control (DAC), see http:// csrc.nist.gov/publications/ nistpubs/800-7/node25.html [13] For more information on the Trusted Computing Platform Alliance (TCPA), see http://www.trustedcomputing. org/home [14] For more information on Linux Security Modules (LSM’s), see http://lsm.immunix.org/ [15] For more information on Security-Enhanced Linux (SE Linux), see http://www.nsa.gov/selinux/ index.cfm [16] For more information on Tripwire, see http://www.tripwire.org/ [17] For more information on AIDE, see http://www.cs.tut.fi/ ~rammer/aide.html [18] For more information on Samhain, see http://la-samhna.de/samhain/ [23] For more information on BestCrypt, see http://www.jetico.com/index. htm#/products.htm [24] For more information on TCFS, see http://www.tcfs.it/ [25] For more information on EncFS, see http://arg0.net/users/ vgough/encfs.html [26] For more information on CryptoFS, see http://reboot.animeirc.de/ cryptofs/ [27] For more information on SSHFS, see http://lufs.sourceforge.net/ lufs/fs.html [28] For more information on the Light-weight Auditing Framework, see http: //lwn.net/Articles/79326/ [29] For more information on Reiser4, see http: //www.namesys.com/v4/v4.html [30] NFSv4 RFC 3010 can be obtained from http://www.ietf.org/rfc/ rfc3010.txt [19] For more information on Logcrypt, see http: //www.lunkwill.org/logcrypt/ [20] For more information on Loop-aes, see http://sourceforge.net/ projects/loop-aes/ [21] For more information on PPDD, see http://linux01.gwdg.de/ ~alatham/ppdd.html [22] For more information on CFS, see http://sourceforge.net/ projects/cfsnfs/
Hotplug Memory and the Linux VM Dave Hansen, Mike Kravetz, with Brad Christiansen IBM Linux Technology Center haveblue@us.ibm.com, kravetz@us.ibm.com, bradc1@us.ibm.com Matt Tolentino Intel matthew.e.tolentino@intel.com Abstract This paper will describe the changes needed to the Linux memory management system to cope with adding or removing RAM from a running system. In addition to support for physically adding or removing DIMMs, there is an everincreasing number of virtualized environments such as UML or the IBM pSeries Hypervisor which can transition RAM between virtual system images, based on need. This paper will describe techniques common to all supported platforms, as well as challenges for specific architectures. 1 Introduction As Free Software Operating Systems continue to expand their scope of use, so do the demands placed upon them. One area of continuing growth for Linux is the adaptation to incessantly changing hardware configurations at runtime. While initially confined to commonly removed devices such as keyboards, digital cameras or hard disks, Linux has recently begun to grow to include the capability to hot-plug integral system components. This paper describes the changes necessary to enable Linux to adapt to dynamic changes in one of the most critical system resource—system RAM. 2 Motivation The underlying reason for wanting to change the amount of RAM is very simple: availability. The systems that support memory hot-plug operations are designed to fulfill mission critical roles; significant enough that the cost of a reboot cycle for the sole purpose of adding or replacing system RAM is simply too expensive. For example, some large ppc64 machines have been reported to take well over thirty minutes for a simple reboot. Therefore, the downtime necessary for an upgrade may compromise the five nine uptime requirement critical to high-end system customers [1]. However, memory hotplug is not just important for big-iron. The availability of high speed, commodity hardware has prompted a resurgence of research into virtual machine monitors—layers of software such as Xen [2], VMWare [3], and conceptually even User Mode Linux that allow for multiple operating system instances to be run in isolated, virtual domains. As computing hardware density has increased, so has the possibility of splitting up that computing power into more manageable pieces. The capability for an operating system to expand or contract the range of physical
Page 1:
Proceedings of the Linux Symposium
Page 4 and 5:
The State of ACPI in the Linux Kern
Page 7 and 8:
Conference Organizers Andrew J. Hut
Page 9 and 10:
TCP Connection Passing Werner Almes
Page 11 and 12:
Linux Symposium 2004 • Volume One
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Cooperative Linux Dan Aloni da-x@co
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Build your own Wireless Access Poin
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Run-time testing of LSB Application
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Linux Block IO—present and future
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Linux AIO Performance and Robustnes
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Methods to Improve Bootup Time in L
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Linux on NUMA Systems Martin J. Bli
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Improving Kernel Performance by Unm
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Linux Virtualization on IBM POWER5
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
The State of ACPI in the Linux Kern
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Scaling Linux® to the Extreme From
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Get More Device Drivers out of the
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Big Servers—2.6 compared to 2.4 W
Page 165 and 166:
Page 167 and 168:
Multi-processor and Frequency Scali
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Dynamic Kernel Module Support: From
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
e100 Weight Reduction Program Writi
Page 205 and 206:
Page 207 and 208:
NFSv4 and rpcsec_gss for linux J. B
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Comparing and Evaluating epoll, sel
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
The (Re)Architecture of the X Windo
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236: Linux Symposium 2004 • Volume One
Page 239 and 240: IA64-Linux perf tools for IO dorks
Page 255 and 256: Carrier Grade Server Features in th
Page 269 and 270: Demands, Solutions, and Improvement
Page 285: Linux Symposium 2004 • Volume One
show all

One - The Linux Kernel Archives

Create successful ePaper yourself

Delete template?

Save as template?