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:04:01 -0400 [thread overview]
Message-ID: <544A7871.7020005@mailservices.uwaterloo.ca> (raw)
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
WARNING: multiple messages have this Message-ID (diff)
From: Ali Abedi <a2abedi@uwaterloo.ca>
To: ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org
Subject: strange MPDU loss pattern
Date: Fri, 24 Oct 2014 12:04:01 -0400 [thread overview]
Message-ID: <544A7871.7020005@mailservices.uwaterloo.ca> (raw)
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
next reply other threads:[~2014-10-24 16:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 16:04 Ali Abedi [this message]
2014-10-24 16:04 ` strange MPDU loss pattern Ali Abedi
2014-10-24 16:13 ` [ath9k-devel] " Kamran Nishat
2014-10-24 16:25 ` Ali Abedi
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=544A7871.7020005@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.