Kconfig.preempt 2.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
  1. choice
  2. prompt "Preemption Model"
  3. default PREEMPT_NONE
  4. config PREEMPT_NONE
  5. bool "No Forced Preemption (Server)"
  6. help
  7. This is the traditional Linux preemption model, geared towards
  8. throughput. It will still provide good latencies most of the
  9. time, but there are no guarantees and occasional longer delays
  10. are possible.
  11. Select this option if you are building a kernel for a server or
  12. scientific/computation system, or if you want to maximize the
  13. raw processing power of the kernel, irrespective of scheduling
  14. latencies.
  15. config PREEMPT_VOLUNTARY
  16. bool "Voluntary Kernel Preemption (Desktop)"
  17. depends on !ARCH_NO_PREEMPT
  18. help
  19. This option reduces the latency of the kernel by adding more
  20. "explicit preemption points" to the kernel code. These new
  21. preemption points have been selected to reduce the maximum
  22. latency of rescheduling, providing faster application reactions,
  23. at the cost of slightly lower throughput.
  24. This allows reaction to interactive events by allowing a
  25. low priority process to voluntarily preempt itself even if it
  26. is in kernel mode executing a system call. This allows
  27. applications to run more 'smoothly' even when the system is
  28. under load.
  29. Select this if you are building a kernel for a desktop system.
  30. config PREEMPT
  31. bool "Preemptible Kernel (Low-Latency Desktop)"
  32. depends on !ARCH_NO_PREEMPT
  33. select PREEMPT_COUNT
  34. select UNINLINE_SPIN_UNLOCK if !ARCH_INLINE_SPIN_UNLOCK
  35. help
  36. This option reduces the latency of the kernel by making
  37. all kernel code (that is not executing in a critical section)
  38. preemptible. This allows reaction to interactive events by
  39. permitting a low priority process to be preempted involuntarily
  40. even if it is in kernel mode executing a system call and would
  41. otherwise not be about to reach a natural preemption point.
  42. This allows applications to run more 'smoothly' even when the
  43. system is under load, at the cost of slightly lower throughput
  44. and a slight runtime overhead to kernel code.
  45. Select this if you are building a kernel for a desktop or
  46. embedded system with latency requirements in the milliseconds
  47. range.
  48. endchoice
  49. config PREEMPT_COUNT
  50. bool