One - The Linux Kernel Archives

More documents

Recommendations

Info

100 • Linux Symposium 2004 • Volume One There has also been the addition of two new page allocation functions: alloc_page_vma() and alloc_page_interleave(). alloc_pages_current() checks that the system is not currently in_interrupt(), and if it isn’t, uses the current process’s process policy for allocation. If the system is currently in interrupt context, alloc_pages_current() falls back to the old default allocation scheme. alloc_page_interleave() allocates pages from regions that are bound with an interleave policy, and is broken out separately because there are some statistics kept for interleaved regions. alloc_page_vma() is a new allocator that allocates only single pages based on a per-vma policy. The alloc_page_vma() function is the only one of the new allocator functions that must be called explicity, so you will notice that some calls to alloc_pages() have been replaced by calls to alloc_page_vma() throughout the kernel, as necessary. 6 Legal statement This work represents the view of the authors, and does not necessarily represent the view of IBM. IBM, NUMA-Q and Sequent are registerd trademarks of International Business Machines Corporation in the United States, other contries, or both. Other company, product, or service names may be trademarks of service names of others. References [LWN] LWN Editor, “Scheduling Domains,” http://lwn.net/Articles/ 80911/ [MM2] Linux 2.6.6-rc2/mm2 source, http: //www.kernel.org 5.5 Problems/Future Work There is no checking that the nodes requested are online at page fault time, so interactions with hotpluggable CPUs/memory will be tricky. There is an asymmetry between how you bind a memory region and a whole process’s memory: One call takes a flags argument, and one doesn’t. Also the maxnode argument is a bit strange, the get/set_affinity calls take a number of bytes to be read/written instead of a maximum CPU number. The alloc_page_ interleave() function could be dropped if we were willing to forgo the statistics that are kept for interleaved regions. Again, a lack of symmetry exists because other types of policies aren’t tracked in any way.
Linux Symposium 2004 • Volume One • 101 Both UP/SMP & NUMA UP/SMP only alloc_page_vma() alloc_page() NUMA only alloc_pages() alloc_pages_current() alloc_pages_node() alloc_page_interleave() __alloc_pages() Figure 9: new alloc_pages
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: Linux Symposium 2004 • Volume One
Page 51 and 52: Linux Block IO—present and future
Page 63 and 64: Linux AIO Performance and Robustnes
Page 79 and 80: Methods to Improve Bootup Time in L
Page 89 and 90: Linux on NUMA Systems Martin J. Bli
Page 99: Linux Symposium 2004 • Volume One
Page 103 and 104: Improving Kernel Performance by Unm
Page 113 and 114: Linux Virtualization on IBM POWER5
Page 121 and 122: The State of ACPI in the Linux Kern
Page 133 and 134: Scaling Linux® to the Extreme From
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:
Page 237 and 238:
Page 239 and 240:
IA64-Linux perf tools for IO dorks
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Carrier Grade Server Features in th
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Demands, Solutions, and Improvement
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Hotplug Memory and the Linux VM Dav
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
show all

One - The Linux Kernel Archives

Create successful ePaper yourself

Delete template?

Save as template?