linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Intel Linux Wireless <ilw@linux.intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] iwlagn: use cts-to-self protection on 5000 adapters series
Date: Mon, 30 May 2011 11:40:32 +0200	[thread overview]
Message-ID: <20110530094031.GA2417@redhat.com> (raw)
In-Reply-To: <BANLkTimoDkE0Cad4cYm2n2B83RxU3GC5zQ@mail.gmail.com>

On Thu, May 26, 2011 at 08:20:58AM -0700, Daniel Halperin wrote:
> On Thu, May 26, 2011 at 7:50 AM, Guy, Wey-Yi <wey-yi.w.guy@intel.com> wrote:
> > On Thu, 2011-05-26 at 08:14 -0700, Stanislaw Gruszka wrote:
> >> diff --git a/drivers/net/wireless/iwlwifi/iwl-agn-hcmd.c b/drivers/net/wireless/iwlwifi/iwl-agn-hcmd.c
> >> index b12c72d..23fa93d 100644
> >> --- a/drivers/net/wireless/iwlwifi/iwl-agn-hcmd.c
> >> +++ b/drivers/net/wireless/iwlwifi/iwl-agn-hcmd.c
> >> @@ -163,17 +163,9 @@ static void iwlagn_tx_cmd_protection(struct iwl_priv *priv,
> >>                                    __le16 fc, __le32 *tx_flags)
> >>  {
> >>       if (info->control.rates[0].flags & IEEE80211_TX_RC_USE_RTS_CTS ||
> >> -         info->control.rates[0].flags & IEEE80211_TX_RC_USE_CTS_PROTECT) {
> >> +         info->control.rates[0].flags & IEEE80211_TX_RC_USE_CTS_PROTECT ||
> >> +         info->flags & IEEE80211_TX_CTL_AMPDU)
> >>               *tx_flags |= TX_CMD_FLG_PROT_REQUIRE_MSK;
> >> -             return;
> >> -     }
> >> -
> >> -     if (priv->cfg->ht_params &&
> >> -         priv->cfg->ht_params->use_rts_for_aggregation &&
> >> -         info->flags & IEEE80211_TX_CTL_AMPDU) {
> >> -             *tx_flags |= TX_CMD_FLG_PROT_REQUIRE_MSK;
> >> -             return;
> >> -     }
> >>  }
> 
> Shouldn't there be a new "use_cts_for_aggregation" flag and one that
> dominates (looks like use_rts in your setup), rather than this?

Not sure if I understand. Rts-cts and cts-to-self are mutual exclusive
at present, so if use_rts_for_aggregations = 0 mean that cts-to-self
protection must be used. Perhaps we should introduce 4-way module
option like: FORCE_RTS_CTS, FORCE_CTS_TO_SELF, FORCE_NO_PROTECTION,
DEFAULT (HW depend) just for doing experiments.

> I'm
> still a bit confused as to why CTS-to-self should help (as opposed to
> masking some other bug).

I have no idea too, and indeed this could mask some (firmware?) bug.
I think I can explain slight better performance on 6000 - when we
use rts-cts two additional frames must be used when starting BA session,
with cts-to-self only one frame.

Anyway 11n on iwlwifi still need some more investigation and fixing.

Stanislaw

  reply	other threads:[~2011-05-30  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 15:14 [PATCH v2] iwlagn: use cts-to-self protection on 5000 adapters series Stanislaw Gruszka
2011-05-26 14:50 ` Guy, Wey-Yi
2011-05-26 15:20   ` Daniel Halperin
2011-05-30  9:40     ` Stanislaw Gruszka [this message]
2011-06-06  8:58   ` Stanislaw Gruszka
2011-06-06 18:21     ` John W. Linville
2011-06-06 21:35       ` Daniel Halperin

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=20110530094031.GA2417@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=dhalperi@cs.washington.edu \
    --cc=ilw@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wey-yi.w.guy@intel.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).