The current TSO segment size accounting code was not taking into account
that the link segment size can be smaller than the maximum segment size
supported by the network card. Without this change, the if_hw_tsomaxsegcount
limit could be ignored, and the mbuf chain created by the TSO code could
indeed have more segments than supported.
Sponsored by: Citrix Systems R&D
Can you replace this with some #define, or at the very least do the math for why 256 is the right length for 1024 bit hash?