linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] mac80211: re-enable aggregation
Date: Mon, 15 Sep 2008 20:30:10 -0700	[thread overview]
Message-ID: <20080916033010.GF659@tesla> (raw)
In-Reply-To: <1221535073-6937-1-git-send-email-lrodriguez@atheros.com>

On Mon, Sep 15, 2008 at 08:17:53PM -0700, Luis Rodriguez wrote:
> Re-enable aggregation by addressing skb->cb overwrites
> after insertion into the qdisc. Aggregation was disabled
> after the new TX multiqueue changes were introduced. Instead
> of relying on the skb->cb we use a new skb->requeue flag
> and an internal mac80211 is_part_amdu().
> 
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> ---
> 
> I haven't tested this patch as its late and I should go home already.
> 
>  drivers/net/wireless/ath9k/main.c         |    2 +-
>  drivers/net/wireless/ath9k/xmit.c         |    2 +-
>  drivers/net/wireless/iwlwifi/iwl-4965.c   |    6 ++++--
>  drivers/net/wireless/iwlwifi/iwl-5000.c   |    6 ++++--
>  drivers/net/wireless/iwlwifi/iwl-agn-rs.c |    8 ++++----
>  drivers/net/wireless/iwlwifi/iwl-tx.c     |    4 ++--
>  include/linux/skbuff.h                    |    4 ++++
>  include/net/mac80211.h                    |   15 ++++++++++++---
>  net/mac80211/main.c                       |    7 ++-----
>  net/mac80211/rx.c                         |    7 ++-----
>  net/mac80211/tx.c                         |    6 ++----
>  net/mac80211/wme.c                        |   19 ++++---------------
>  12 files changed, 42 insertions(+), 44 deletions(-)
> 
> diff --git a/drivers/net/wireless/ath9k/main.c b/drivers/net/wireless/ath9k/main.c
> index c5107f2..878e45f 100644
> --- a/drivers/net/wireless/ath9k/main.c
> +++ b/drivers/net/wireless/ath9k/main.c
> @@ -1241,7 +1241,7 @@ static int ath_attach(u16 devid,
>         /* FIXME: Have to figure out proper hw init values later */
> 
>         hw->queues = 4;
> -       hw->ampdu_queues = 1;
> +       hw->ampdu_queues = 8;

Ignore this hunk ;) We just have to figure out why we are using a
tid for the AP after we assign our IP address. This is also why this
"ampdu queue" for aggregation is kind of ackward.

  Luis

  reply	other threads:[~2008-09-16  3:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16  3:17 [PATCH v2] mac80211: re-enable aggregation Luis R. Rodriguez
2008-09-16  3:30 ` Luis R. Rodriguez [this message]
2008-09-16  6:37 ` Johannes Berg
2008-09-17 20:57   ` Tomas Winkler
2008-09-17 22:45     ` Luis R. Rodriguez
2008-09-17 22:57       ` Tomas Winkler
2008-09-17 23:03         ` Luis R. Rodriguez
2008-09-17 23:05           ` Johannes Berg
2008-09-17 23:20             ` Tomas Winkler
2008-09-17 23:45               ` Tomas Winkler
  -- strict thread matches above, loose matches on Subject: below --
2008-10-21  7:14 [PATCH v2] mac80211: Re-enable aggregation Sujith
2008-10-21  7:24 ` Johannes Berg

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=20080916033010.GF659@tesla \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).