Page MenuHomeFreeBSD

Use public interfaces to manage the nested rate limit send tag.
ClosedPublic

Authored by jhb on Oct 28 2020, 11:51 PM.
Tags
None
Referenced Files
Unknown Object (File)
Oct 23 2024, 12:46 PM
Unknown Object (File)
Oct 4 2024, 7:32 PM
Unknown Object (File)
Oct 4 2024, 11:48 AM
Unknown Object (File)
Oct 4 2024, 8:50 AM
Unknown Object (File)
Oct 1 2024, 2:30 PM
Unknown Object (File)
Sep 29 2024, 9:30 PM
Unknown Object (File)
Sep 28 2024, 7:37 PM
Unknown Object (File)
Sep 18 2024, 8:04 PM
Subscribers

Details

Summary

Each TLS send tag in mlx5 contains a nested rate limit send tag.
Previously, the driver was calling internal functions to manage the
nested tag. Calling free methods directly instead of m_snd_tag_rele()
leaked send tag references and references on the ifp. Changes to use
the ifp methods for the nested tag for other methods are more cosmetic
but do simplify the code.

Test Plan
  • Drew tested a smaller version of this patch (mostly the m_snd_tag_rele bits)

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jhb requested review of this revision.Oct 28 2020, 11:51 PM
This revision is now accepted and ready to land.Oct 29 2020, 12:12 AM
sys/dev/mlx5/mlx5_en/mlx5_en_hw_tls.c
450 ↗(On Diff #78874)

you probably can also remove all instances of && defined(IF_SND_TAG_TYPE_TLS_RATE_LIMIT)

sys/dev/mlx5/mlx5_en/mlx5_en_hw_tls.c
450 ↗(On Diff #78874)

True. I will create a review to do that as a separate commit in a bit.