All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ali Abedi <a2abedi@uwaterloo.ca>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] strange MPDU loss pattern
Date: Fri, 24 Oct 2014 12:25:04 -0400	[thread overview]
Message-ID: <544A7D60.9090605@mailservices.uwaterloo.ca> (raw)
In-Reply-To: <CADxDmp5NofUAgcdHqfwuDLfxfFhhtj-02FQ-NWcKvfE-Eh7sCg@mail.gmail.com>

Hi,

Yes we look at the BA bitmap and also too we have printks in the driver 
that
tells us what happened to the MPDUs in an aggregated frame.

Thanks,
Ali


On 24/10/2014 12:13 PM, Kamran Nishat wrote:
> How did u determine that? only by looking at the Bitmaps in BlockAcks?
>
> On Fri, Oct 24, 2014 at 9:04 PM, Ali Abedi <a2abedi@uwaterloo.ca 
> <mailto: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
>     _______________________________________________
>     ath9k-devel mailing list
>     ath9k-devel at lists.ath9k.org <mailto:ath9k-devel@lists.ath9k.org>
>     https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20141024/fca5fb5f/attachment.htm 

  reply	other threads:[~2014-10-24 16:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 16:04 [ath9k-devel] strange MPDU loss pattern Ali Abedi
2014-10-24 16:04 ` Ali Abedi
2014-10-24 16:13 ` [ath9k-devel] " Kamran Nishat
2014-10-24 16:25   ` Ali Abedi [this message]
2014-10-24 19:13 ` Adrian Chadd
2014-10-24 19:13   ` Adrian Chadd
2014-10-24 19:23   ` [ath9k-devel] " Kamran Nishat
2014-10-24 19:23     ` Kamran Nishat
2014-10-24 20:37     ` Krishna Chaitanya
2014-10-24 20:37       ` Krishna Chaitanya
2014-10-24 20:42   ` Ali Abedi
2014-10-24 20:42     ` Ali Abedi
2014-10-25 15:19     ` [ath9k-devel] " Adrian Chadd
2014-10-25 15:19       ` Adrian Chadd
2014-10-25 15:28       ` [ath9k-devel] " Ali Abedi
2014-10-25 15:28         ` Ali Abedi
2014-10-25 18:30         ` [ath9k-devel] " Adrian Chadd
2014-10-25 18:30           ` Adrian Chadd
2014-10-25 20:35           ` [ath9k-devel] " Ali Abedi
     [not found]             ` <CAETUFS8iDDcrPwu_NCV4Ks9Mq6KUjqdujVyyZ5Y6om=14J+B9g@mail.gmail.com>
2014-10-27  1:50               ` Ali Abedi
2014-10-27 12:05               ` Felix Fietkau
2014-10-27 12:05                 ` Felix Fietkau
2014-10-29 20:34             ` Adrian Chadd
2014-10-29 20:34               ` Adrian Chadd
2014-10-30 15:48               ` [ath9k-devel] " Ali Abedi
2014-10-30 15:48                 ` Ali Abedi
2014-10-30 16:11                 ` [ath9k-devel] " Adrian Chadd
2014-10-30 16:11                   ` Adrian Chadd
2014-10-30 16:20                   ` [ath9k-devel] " Ali Abedi
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=544A7D60.9090605@mailservices.uwaterloo.ca \
    --to=a2abedi@uwaterloo.ca \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.