linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT 00/11] mac80211: enable fast-xmit and some offloads
Date: Tue, 14 Apr 2015 17:13:47 +0200	[thread overview]
Message-ID: <1429024427.3019.18.camel@sipsolutions.net> (raw)
In-Reply-To: <1429023829-3991-1-git-send-email-johannes@sipsolutions.net> (sfid-20150414_170402_357343_42C8C498)

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


      parent reply	other threads:[~2015-04-14 15:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 15:03 [RFC/RFT 00/11] mac80211: enable fast-xmit and some offloads Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 01/11] mac80211: add TX fastpath Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 02/11] mac80211_hwsim: enable IEEE80211_HW_SUPPORT_FAST_XMIT Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 03/11] mac80211: extend fast-xmit to driver fragmentation Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 04/11] mac80211: extend fast-xmit for more ciphers Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 05/11] mac80211: extend fast-xmit to cover IBSS Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 06/11] wlcore: enable IEEE80211_HW_SUPPORT_FAST_XMIT Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 07/11] ath10k: " Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 08/11] mac80211: allow checksum offload only in fast-xmit Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 09/11] mac80211: enable changing netdev features with ethtool Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 10/11] mac80211: allow drivers to support S/G Johannes Berg
2015-04-14 15:03 ` [RFC/RFT 11/11] mac80211: allow segmenation offloads Johannes Berg
2015-04-14 15:13 ` Johannes Berg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1429024427.3019.18.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).