One - The Linux Kernel Archives

More documents

Recommendations

Info

200 • Linux Symposium 2004 • Volume One applied to the module source before a module build occurs. In this way, by including various patches needed for various kernel versions, you can distribute one source tarball and ensure it will always properly build regardless of the end user target kernel. If no corresponding PATCH_MATCH[0] entry were specified for PATCH[0], then the adriver.h.patch would always get applied before a module build. As DKMS always starts off each module build with pristine module source, you can always ensure the right patches are being applied. Also seen in this example is: MODULES_CONF[0]= "alias char-major-116 snd" MODULES_CONF[1]= "alias snd-card-0 snd-intel8x0" Unlike the previous discussion of /etc/modules.conf changes, any entries placed into the MODULES_CONF array are automatically added into /etc/modules.conf during a module install. These are later only removed during the final module uninstall. Lastly, we have: POST_INSTALL="alsa-driver-dkms-post.sh" In the event that you have other scripts that must be run during various DKMS events, DKMS includes POST_ADD, POST_BUILD, POST_INSTALL and POST_REMOVE functionality. 7 Future As you can tell from the above, DKMS is very much ready for deployment now. However, as with all software projects, there’s room for improvement. 7.1 Cross-Architecture Builds DKMS today has no concept of a platform architecture such as i386, x86_64, ia64, sparc, and the like. It expects that it is building kernel modules with a native compiler, not a cross compiler, and that the target architecture is the native architecture. While this works in practice, it would be convenient if DKMS were able to be used to build kernel modules for nonnative architectures. Today DKMS handles the cross-architecture build process by having separate /var/dkms directory trees for each architecture, and using the dkmstree option to specify a using a different tree, and the config option to specify to use a different kernel configuration file. Going forward, we plan to add an −−arch option to DKMS, or have it glean it from the kernel config file and act accordingly. 7.2 Additional distribution driver disks DKMS today supports generating driver disks in the Red Hat format only. We recognize that other distributions accomplish the same goal using other driver disk formats. This should be relatively simple to add once we understand what the additional formats are. 8 Conclusion DKMS provides a simple and unified mechanism for driver authors, Linux distributions, system vendors, and system administrators to update the device drivers on a target system without updating the whole kernel. It allows driver developers to keep their work aimed at the “top of the tree,” and to backport that work to older kernels painlessly. It allows Linux distributions to provide updates to single device drivers asynchronous to the release of a larger
Linux Symposium 2004 • Volume One • 201 scheduled update, and to know what drivers have been updated. It lets system vendors ship newer hardware than was supported in a distribution’s “gold” release without invalidating any test or certification work done on the “gold” release. It lets system administrators update individual drivers to match their environment and their needs, regardless of whose kernel they are running. It lets end users track which module versions have been added to their system. We believe DKMS is a project whose time has come, and encourage everyone to use it. 9 References DKMS is licensed under the GNU General Public License. It is available at http://linux.dell.com/dkms/, and has a mailing list dkms-devel@ lists.us.dell.com to which you may subscribe at http://lists.us.dell. com/.
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: Linux Symposium 2004 • Volume One
Page 163 and 164: Big Servers—2.6 compared to 2.4 W
Page 167 and 168: Multi-processor and Frequency Scali
Page 187 and 188: Dynamic Kernel Module Support: From
Page 199: Linux Symposium 2004 • Volume One
Page 203 and 204: e100 Weight Reduction Program Writi
Page 207 and 208: NFSv4 and rpcsec_gss for linux J. B
Page 215 and 216: Comparing and Evaluating epoll, sel
Page 227 and 228: The (Re)Architecture of the X Windo
Page 239 and 240: IA64-Linux perf tools for IO dorks
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?