linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ali Abedi <a2abedi@uwaterloo.ca>
To: Adrian Chadd <adrian@freebsd.org>
Cc: ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org
Subject: Re: strange MPDU loss pattern
Date: Fri, 24 Oct 2014 16:42:32 -0400	[thread overview]
Message-ID: <544AB9B8.9050407@mailservices.uwaterloo.ca> (raw)
In-Reply-To: <CAJ-Vmon_jefxRgZvJmOsr4ydNHbvTCyMHHejRMWqXg_SG6NJUw@mail.gmail.com>

We don't use a rate adaptation at this moment (i.e., fixed rate) and the 
setup
  is stationary. So we expect to see relatively stable channel 
conditions. Even if the channel
conditions change during the aggregated frame. The first half of the MPDUs
have the same chance of experiencing worse channel conditions.

Thank,
Ali


On 14-10-24 03:13 PM, Adrian Chadd wrote:
> It's not completely unsurprising - the initial channel estimate and
> such is done at the beginning of each packet and stays constant. So if
> there's some varying channel conditions that change that during the
> duration of a packet, the tail end is going to end up having less SNR
> and may end up getting more errors.
>
>
> -adrian
>
> On 24 October 2014 09:04, Ali Abedi <a2abedi@uwaterloo.ca> wrote:
>> Hello,
>>
>> We study the effects of 802.11n frame aggregation on throughput. We noticed
>> a
>> strange pattern in the MPDU loss within an aggregated frame. It seems that
>> the
>> second half of the MPDUs (those with higher sequence numbers) in an
>> aggregated frame
>> are more likely to be lost. Is this a known fact or is there any explanation
>> for it?
>>
>> For example if 32 frames are aggregated with sequence numbers 100 to 131.
>> Frames with sequence numbers 100-115 are more likely to be received
>> correctly
>> than 116-131.
>>
>>
>> Best,
>> Ali
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2014-10-24 20:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 16:04 strange MPDU loss pattern Ali Abedi
2014-10-24 19:13 ` Adrian Chadd
2014-10-24 19:23   ` [ath9k-devel] " Kamran Nishat
2014-10-24 20:37     ` Krishna Chaitanya
2014-10-24 20:42   ` Ali Abedi [this message]
2014-10-25 15:19     ` Adrian Chadd
2014-10-25 15:28       ` Ali Abedi
2014-10-25 18:30         ` Adrian Chadd
     [not found]           ` <544C0995.8010507@mailservices.uwaterloo.ca>
     [not found]             ` <CAETUFS8iDDcrPwu_NCV4Ks9Mq6KUjqdujVyyZ5Y6om=14J+B9g@mail.gmail.com>
2014-10-27 12:05               ` [ath9k-devel] " Felix Fietkau
2014-10-29 20:34             ` Adrian Chadd
2014-10-30 15:48               ` Ali Abedi
2014-10-30 16:11                 ` Adrian Chadd
2014-10-30 16:20                   ` Ali Abedi

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=544AB9B8.9050407@mailservices.uwaterloo.ca \
    --to=a2abedi@uwaterloo.ca \
    --cc=adrian@freebsd.org \
    --cc=ath9k-devel@venema.h4ckr.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).