793e6c8319
Just explain what isolated_cores= is for and recommend to only have one isolated_cores= line to avoid wrong system configuration. Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
31 lines
1 KiB
Text
31 lines
1 KiB
Text
#
|
|
# Core isolation
|
|
#
|
|
# The 'isolated_cores=' variable below controls which cores should be
|
|
# isolated. By default we reserve 1 core per socket for housekeeping
|
|
# and isolate the rest. But you can isolate any range as shown in the
|
|
# examples below. Just remember to keep only one isolated_cores= line.
|
|
#
|
|
# Examples:
|
|
# isolated_cores=2,4-7
|
|
# isolated_cores=2-23
|
|
#
|
|
# Reserve 1 core per socket for housekeeping, isolate the rest.
|
|
# Change this for a core list or range as shown above.
|
|
isolated_cores=${f:calc_isolated_cores:1}
|
|
|
|
#
|
|
# Uncomment the 'isolate_managed_irq=Y' bellow if you want to move kernel
|
|
# managed IRQs out of isolated cores. Note that this requires kernel
|
|
# support. Please only specify this parameter if you are sure that the
|
|
# kernel supports it.
|
|
#
|
|
isolate_managed_irq=Y
|
|
|
|
#
|
|
# Set the desired combined queue count value using the parameter provided
|
|
# below. Ideally this should be set to the number of housekeeping CPUs i.e.,
|
|
# in the example given below it is assumed that the system has 4 housekeeping
|
|
# (non-isolated) CPUs.
|
|
#
|
|
# netdev_queue_count=4
|