Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
kernel [2015/05/22 03:35] slackermedia [Low Latency Kernel] |
kernel [2021/09/01 02:23] (current) slackermedia |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | [[{arrowp.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;left:0;}dep|]] | ||
| - | |||
| - | [[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;margin-left:2.5em;}sound|]] | ||
| - | |||
| - | |||
| ====== Low Latency Kernel ====== | ====== Low Latency Kernel ====== | ||
| Line 9: | Line 4: | ||
| **TL;DR** \\ | **TL;DR** \\ | ||
| Give applications permission to not play nice with others: ''/sbin/setcap cap_ipc_lock,cap_sys_nice=ep /path/to/greedy/application'' | Give applications permission to not play nice with others: ''/sbin/setcap cap_ipc_lock,cap_sys_nice=ep /path/to/greedy/application'' | ||
| + | </WRAP> | ||
| A computer's CPU does //a lot//, cycling constantly through series of loops and commands and probes and checks and refreshes and updates so consistently that sys admin even today talk in terms of "CPU cycles" when estimating the "cost" of a computationally intensive project. Regardless of what you do artistically on your computer, yours is no exception: the CPU is in high demand every second, and not everything demanding its attention can be tended to at the same time. For this reason, the driver of the CPU (the "kernel") queues all tasks needing attention, delegates priorities to each one, and then executes chunks of each waiting task according to priority. This happens millions times per second. | A computer's CPU does //a lot//, cycling constantly through series of loops and commands and probes and checks and refreshes and updates so consistently that sys admin even today talk in terms of "CPU cycles" when estimating the "cost" of a computationally intensive project. Regardless of what you do artistically on your computer, yours is no exception: the CPU is in high demand every second, and not everything demanding its attention can be tended to at the same time. For this reason, the driver of the CPU (the "kernel") queues all tasks needing attention, delegates priorities to each one, and then executes chunks of each waiting task according to priority. This happens millions times per second. | ||
| Line 37: | Line 33: | ||
| * The DAW(s) that you use. | * The DAW(s) that you use. | ||
| * Loopers, beatboxes, drum machines, sequencers. | * Loopers, beatboxes, drum machines, sequencers. | ||
| + | * Ffmpeg, if you intend to do screen captures with it. | ||
| + | |||
| You do not need to worry about getting everything all at once; if something needs to be //less nice// with other processes, you'll hear it. You can whitelist it as needed, and the change will be immediate. | You do not need to worry about getting everything all at once; if something needs to be //less nice// with other processes, you'll hear it. You can whitelist it as needed, and the change will be immediate. | ||
| + | |||
| + | <WRAP important> | ||
| + | If you came here for a low latency kernel, that's it! you're done. You can skip the next section. | ||
| + | </WRAP> | ||
| + | |||
| ====== Realtime Kernel ====== | ====== Realtime Kernel ====== | ||
| Line 48: | Line 51: | ||
| -The kernel source code | -The kernel source code | ||
| -Realtime patches for the source code | -Realtime patches for the source code | ||
| - | |||
| ===== Patching the Kernel ===== | ===== Patching the Kernel ===== | ||
| Line 106: | Line 108: | ||
| <code> | <code> | ||
| - | # cp /media/cdrom/testing/source/ linux-X.X.XX.X-configs/config-generic-smp-X.X.XX.X-smp /path/to/linux-X.X.XX.X/.config | + | # cp /media/cdrom/testing/source\ |
| + | /linux-X.X.XX.X-configs/config-generic-smp-X.X.XX.X-smp \ | ||
| + | /path/to/linux-X.X.XX.X/.config | ||
| </code> | </code> | ||
| Line 112: | Line 116: | ||
| Launch ''menuconfig'', an ncurses-based, menu-driven list of possible options for your new kernel. The menu can be overwhelming, but as it starts off with the default Slackware configuration, there will not be much you need to change, but for the realtime options. | Launch ''menuconfig'', an ncurses-based, menu-driven list of possible options for your new kernel. The menu can be overwhelming, but as it starts off with the default Slackware configuration, there will not be much you need to change, but for the realtime options. | ||
| + | |||
| + | <code> | ||
| + | # make menuconfig | ||
| + | </code> | ||
| Most of the realtime options can be found in the **Processor type and features** menu. | Most of the realtime options can be found in the **Processor type and features** menu. | ||
| Line 222: | Line 230: | ||
| - | [[{arrown.png|border:0;background:none;width:0;display:inline-block;float:right;}sound|]][[{arrowp.png|border:0;background:none;width:0;float:right;}dep|]] | + | <WRAP centeralign> |
| + | <wrap fa>[[ffmpeginstall|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[dvd|Q]]</wrap> | ||
| + | </WRAP> | ||