Project

General

Profile

Actions

New Content #12237

open

Add information on ``ifqmaxlen`` to Hardware Tuning and Troubleshooting

Added by Viktor Gurov over 1 year ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Hardware
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Page: https://docs.netgate.com/pfsense/en/latest/hardware/tune.html

Feedback:

Need to add optimization of interface queue length (net.link.ifqmaxlen), see #10311 for details

Actions #1

Updated by Jim Pingle 7 months ago

  • Tracker changed from Todo to New Content
  • Subject changed from Feedback on Hardware — Hardware Tuning and Troubleshooting to Add information on ``ifqmaxlen`` to Hardware Tuning and Troubleshooting
Actions #2

Updated by Chris W 5 months ago

It looks like this is the source of the 2048 figure given in #10311. Calomel arrives at that by doubling the value of inline hw.igb.txd, which is exclusive to igb and em network interfaces. It doesn't look like igc, vtnet, mvneta, or ix, have this value or a single equivalent, but devices with those interfaces do show inline net.link.ifqmaxlen=128 as default. This is in 22.05 on an 1100, 4100, 5100, and KVM-based virtual machine.

Unless there's some other tunable(s) which makes use of inline net.link.ifqmaxlen on non-(if_em) interfaces, it looks like we need to specify that this only applies to those two network interface types. Is that correct?

Actions

Also available in: Atom PDF