On Tue, 2015-04-14 at 17:03 +0200, Johannes Berg wrote:
> First, add the TX fastpath ("fast-xmit") that I've been kicking around for
> a while. I'm pretty happy with the abstraction since it allows me to not
> have to worry about a lot of details in the regular TX path...
>
> Secondly, I want to enable more offloads. So the first thing to do is to
> actually fix checksum offload - the TI driver has a bug in that if it fails
> to upload keys or so, checksums will be completely bogus.
>
> So the first step to fix that bug is to enable checksum offload only on
> the fast-xmit path, while having a software fallback on the regular TX path
> to make software crypto etc. do the right thing. To not cause regressions
> for the TI/ath10k drivers, this requires extending fast-xmit to cover more
> cases, but that's easy.
>
> Secondly then, we can add code to do in software what the driver might do,
> which is actually what the network stack does for us anyway today, but now
> we can do it only on the non-fast-xmit path so that the fast-xmit path can
> pass packets with required checksumming or segmentation to the device.
>
> So far I've only tested the software fallbacks, not the actual hardware
> offloads.
Forgot to say - for those who do want to play with this, this is also
available in my mac80211-next tree in the fast-xmit branch.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
