AXP(4)
π AXP(4) π
okay so bestie, let me tell you about axp from the Kernel Interfaces Manual β she's the Advanced Micro Devices 10G Ethernet driver and she is literally iconic β¨
π NAME π
axp β the Advanced Micro Devices 10G Ethernet driver, no cap π
π¦ SYNOPSIS π¦
so if you wanna compile this driver right into your kernel (main character energy), you drop these lines into your kernel configuration file:
device iflib
device axp
OR β and this is the lowkey easier way β you can load the driver as a module at boot time by putting this line in loader.conf(5):
if_axp_load="YES"
slay, that's it π«Ά
β¨ DESCRIPTION β¨
okay so the axp driver enables the PCI-E based 10G Ethernet controller that's inbuilt in the AMD EPYC processors. she's built different fr fr π
here's everything she supports, and yes, you're gonna be obsessed:
- 1G/10G SFP+ Link π
- Jumbo frames (9000 Bytes) β big packets, big vibes π
- Transmit and Receive checksum offload π₯
- TCP segmentation offload (TSO) π
- VLAN tag insertion/extraction π
- VLAN checksum offload π
- VLAN TSO β¨
- Receive side steering (RSS) π¦
- IPV4 and IPV6 capable β
- MSI-X interrupts π
- Split header πΈ
and the bestie part? all the above mentioned features are enabled by default β they just work, no extra effort required, periodt π
for hardware related questions, please refer the documentation supplied along with AMD EPYC processors π (don't come for me, I just work here)
πΊ SYSCTL VARIABLES πΊ
the following variables are available as sysctl(8) variables β these are your little windows into how she's doing, iykyk:
dev.ax.X.mac_statsβ dumps the transmit and receive statistics counter values for the controller. this includes statistics specific to each transmit and receive queue. she's giving transparency πdev.ax.X.channels_infoβ dumps the permissible and default configured transmit and receive channel information. iconic πdev.ax.X.ringparam_infoβ dumps the permissible and default configured descriptor information for the transmit and receive queue. the way she just tells you things π¦dev.ax.X.link_ksettings_infoβ dumps the current link setting like link mode, speed, duplex settings. she's an open book fr fr β¨dev.ax.X.pauseparam_infoβ dumps the current flow-control settings. lowkey obsessed with how organized she is πΈdev.ax.X.coalesce_infoβ dumps the current interrupt coalescing settings. πdev.ax.X.link_infoβ dumps the current state of the Link. let you know what's up πdev.ax.X.drv_infoβ dumps the driver and controller firmware version information. the receipts, bestie πdev.ax.X.YYYY_registerdev.ax.X.YYYY_register_valuesβ sysctl to dump a specific register from a specific block of the controller.YYYYspecifies the block. the following blocks are supported:xpcsxgmacxpropxi2c
set the offset of the register to the first variable, and then read the value of the register by reading the second variable. big brain energy, I know π§
dev.ax.X.axgbe_debug_levelβ configure the log-level for the driver. default is0. supports0-3. turn up the volume on those logs bestie π₯dev.ax.X.link_workaroundβ this variable enables the workaround for an intermittent link issue. when link does not come up for long time, this variable can be set to1to reset the phy and bring up the link. she's a lil dramatic sometimes but we fix her π
π¦ LOADER TUNABLES π¦
the following variable is available as loader.conf(5) tunable:
dev.ax.X.sph_enableβ this variable controls split header feature for the interface. default is1, meaning the split header support is enabled. she's on by default, as she should be π
wait bestie, important: this variable must be set before loading the driver, either via loader.conf(5) or through kenv(1). this cannot be modified when driver is loaded. no take-backsies π
setting this variable in loader.conf(5) needs the system to be restarted to take effect. when using kenv(1), use the wrapper variable dev.ax.sph_enable, which will configure(enable/disable) split header support for all axp interfaces. one ring to rule them all fr fr π
to use netmap with this device, split header support must be disabled (set this variable to 0). no exceptions, bestie π
π SEE ALSO π
the squad, the ensemble cast, the supporting characters:
arp(4), iflib(4), netmap(4), vlan(4), ifconfig(8) β¨
π HISTORY π
the axp device driver first appeared in FreeBSD 13.0. she's not new to this, she's true to this π
okay so there's lore here β another version of the driver is already present in FreeBSD. this driver was named as "axgbe" earlier, which is renamed as "axa" now. this driver is for the ACPI based Ethernet controllers in the previous/older version of the hardware. this driver is authored by β¨andrew@FreeBSD.orgβ©. the family tree is giving complicated but we respect the lineage πΈ
π AUTHORS π
the axp device driver was written by Advanced Micro Devices Inc. β AMD said "we'll do it ourselves" and honestly? they ate π₯
for any issues and support requirements, email the details to β¨rajesh1.kumar@amd.comβ©. shoot your shot bestie, they wanna help π
Debian | February 19, 2021 β that's the version and date of this iconic little manual page, mwah π
π¦ where this page comes from
- freebsd 14.5: base 14.5
- freebsd 15.1: base 15.1
- nixpkgs unstable: source
- Copyright (c) 2020, Advanced Micro Devices Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms