linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>,
	"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Always send management frames at MCS-0??
Date: Tue, 10 Sep 2013 09:49:54 -0500	[thread overview]
Message-ID: <1378824594.6741.2.camel@dcbw.foobar.com> (raw)
In-Reply-To: <CABPxzYKcVyomdXaDxT3mLXQb0sYfM=UdoZwpbsb4qohTkPU3Cw@mail.gmail.com>

On Tue, 2013-09-10 at 14:47 +0530, Krishna Chaitanya wrote:
> On Tue, Sep 10, 2013 at 4:40 AM, Ben Greear <greearb@candelatech.com> wrote:
> 
> > Would forcing them to a lower rate at least theoretically improve
> > the chance that the packets are properly delivered?
> Yes. But we already have a RC algorithm taking care of that.
> Right?

Except if there's periodic interference, like a microwave.  In this
case, where the microwave cycles on and off, the longer it takes to
transmit the frame (ie, a lower rate) the *more* likely it is to get
partially squelched by the microwave turning on in its next cycle.  Here
a faster rate can be more robust since it can transmit the entire frame
in between microwave cycles.

Dan


  reply	other threads:[~2013-09-10 14:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 19:10 Always send management frames at MCS-0?? Ben Greear
2013-09-09 19:15 ` Krishna Chaitanya
2013-09-09 23:10   ` Ben Greear
2013-09-10  9:17     ` Krishna Chaitanya
2013-09-10 14:49       ` Dan Williams [this message]
2013-09-10  8:10 ` Sujith Manoharan
2013-09-10 15:48   ` Ben Greear
2013-09-11  9:33     ` Felix Fietkau

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=1378824594.6741.2.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=chaitanya.mgit@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=hostap@lists.shmoo.com \
    --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).