<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ports on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.04/en/tags/ports/</link>
    <description>Recent content in Ports on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.04/en/tags/ports/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Core Isolation for Performance Optimization</title>
      <link>https://docs.mitigator.ru/v26.04/en/kb/isolcpus/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/kb/isolcpus/</guid>
      <description>By default, the CPU cores that work with network ports are also used by other subsystems. This can degrade performance and cause Input Errors pps/bps spikes on Port extX/intX graphs. You can take some of the load off these cores by preventing non-critical subsystems from running on them.
To do so:
Specify isolation of the packet processor cores in the core options through the isolcpus=... and rcu_nocbs=... parameters. It is also recommended to add mitigations=off to disable core security patches.</description>
    </item>
  </channel>
</rss>