ACCEL-CONFIG-CONFIG-GROUP(1)

πŸ’– accel-config-config-group β€” the glow-up page πŸ’–

okay so bestie, this is part of the accfg Manual β€” yeah, that ACCEL-CONFIG CONFIG(1) energy, we love her. this page is literally all about accel-config-config-group, which is the little command that lets you tweak the individual attributes of a group. one group, all her settings, you're basically her stylist πŸ’…


✨ NAME ✨

accel-config-config-group β€” configure individual attributes of a group πŸŽ€


🌸 SYNOPSIS 🌸

accel-config config-group <device name>/<group name> [<options>]

πŸ¦‹ EXAMPLE πŸ¦‹

here's the moment, the serve, the demo:

accel-config config-group dsa0/group0.0 --read-buffers-reserved=1

like. look at her go. πŸ˜­πŸ’–


πŸ‘‘ OPTIONS πŸ‘‘

okay this is the part where we list every single flag, no skipping, no gatekeeping, fr fr:

  • -r, --read-buffers-reserved= β€” set how many read buffers get reserved for the engines in this group. and the limits? the limits are giving βœ‹:
    • the sum of all read-buffers-reserved across all groups has to be less than or equal to the total read buffers from the group capability field of the device. no cap.
  • -t, --read-buffers-allowed= β€” set the max number of read buffers that all the engines in the group can have in use at the same time. basically a bandwidth ceiling for the group, so she doesn't eat the whole snack table. and the limit of this value must be:
    • greater than 0
    • greater than or equal to the read-buffers-reserved value for this group
    • less than or equal to the sum of the read-buffers reserved field and the non-reserved read buffers (total read buffers - total read buffers reserved for all groups)
  • -l, --use-read-buffer-limit= β€” toggles whether the read-buffer limit is enabled or not. use-read-buffer-limit should be either 0 or 1. that's it, that's the toggle. slay.
  • -a, --traffic-class-a= β€” sets traffic class A for this group. it should be larger than 0 and less than 8.
  • -b, --traffic-class-b= β€” sets traffic class B for this group. it should be larger than 0 and less than 8.
  • -d, --desc-progress-limit= β€” controls how many work descriptors an engine in the group can have processed concurrently. range of valid values are 0, 1, 2 and 3 for max, 1/2, 1/4 and 1/8 respectively that the engine is capable of. iykyk 🌈
  • -p, --batch-progress-limit= β€” controls how many batch descriptors an engine in the group can have processed concurrently. range of valid values are 0, 1, 2 and 3 for max, 1/2, 1/4 and 1/8 respectively that the engine is capable of.
bestie pls note: those reserved-vs-allowed constraints are doing a whole vibe check on each other β€” if you set them wrong, it's not the move. πŸ’€

Copyright (c) 2023 - 2026, Intel Corporation. License GPLv2: GNU GPL version 2 http://gnu.org/licenses/gpl.html. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

like, go off, remix it, redistribute it, that's the whole point 🫢 (just, y'know, no warranty. the lawyers said so. 😭)


and that's the page, bestie!! ✨ courtesy of accfg 4.1.8+, dated 07/23/2026 β€” mwah, iconic, periodt. πŸ’…πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from