Multi-Queue
By default, each network interface has one traffic queue handled by one CPU.
You cannot use more CPU cores for acceleration than the number of interfaces handling traffic.
Multi-Queue An acceleration feature on Security Gateway that configures more than one traffic queue for each network interface. Multi-Queue assigns more than one receive packet queue (RX Queue) and more than one transmit packet queue (TX Queue) to an interface. Multi-Queue is applicable only if SecureXL is enabled (this is the default). Acronym: MQ. configures more than one traffic queue for each network interface.
For each interface, more than one CPU core is used for acceleration.
|
Note - Multi-Queue is applicable only if SecureXL Check Point product on a Security Gateway that accelerates IPv4 and IPv6 traffic that passes through a Security Gateway. is enabled (this is the default). |
Overview:
-
Multi-Queue is enabled by default on all interfaces that use the supported drivers.
-
The number of traffic queues on each supported interface is determined automatically, based on:
-
The number of available CPU cores that run CoreXL Performance-enhancing technology for Security Gateways on multi-core processing platforms. Multiple Check Point Firewall instances are running in parallel on multiple CPU cores. SND Instances.
-
The limitations of the interfaces and its driver.
-
-
Traffic queues are automatically affined to the CPU cores that runs CoreXL SND Instances.
-
Changes in Multi-Queue configuration do not require a reboot.
-
You configure Multi-Queue on the command line - either in Gaia Clish The name of the default command line shell in Check Point Gaia operating system. This is a restricted shell (role-based administration controls the number of commands available in the shell)., or in the Expert mode.