From: Peizhao Hu <peizhao.research@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Wei Yin <yinwei@itee.uq.edu.au>
Subject: questions regarding the minstrel implementation on mac80211
Date: Tue, 12 Apr 2011 09:24:07 +1000 [thread overview]
Message-ID: <4DA38D97.1030407@gmail.com> (raw)
Hi all,
I am studying the minstrel rate control mechinsim in mac80211. I have
observed a few strange problem with the current implementation of the
minstrel on the mac80211. They are explained below:
1. Different DIFS values were used by madwifi 0.9.4 and mac80211.
In madwifi 0.9.4, the DIFS is set to 28 from the source code in the
calc_usecs_unicast_packet() function.
However, according to the IEEE 802.11 2007 standard, the DIFS time for
OFDM should be 34, which is 2 slot time plus a SIFS time shown in table
17-15 in page 626 or described in page 271.
Why we have different DIFS values?
2. Another question is on how we calculate the frame transmission time
In the function "ieee80211_frame_duration()" within util.c on the
mac80211 framework, the frame time is calculated as the following.
dur = 16; /* SIFS + signal ext */
dur += 16; /* T_PREAMBLE = 16 usec */
dur += 4; /* T_SIGNAL = 4 usec */
dur += 4 * DIV_ROUND_UP((16 + 8 * (len + 4) + 6) * 10, 4 * rate); /*
T_SYM x N_SYM */
In mac80211 based minstrel implementation, minstrel uses the able
fuction to calculate the time for sending a data frame as well as
sending an ack.
to our understanding the normal transmission time is calculated as below
(assume no retransmission):
DIFS + contentionWindow + dataTime + SIFS + ackTime
where
dataTime=T_PREAMBLE + T_SIGNAL + T_SYM * N_SYM
ackTime is similar
but in Minstrel's implementation (using the above
"ieee80211_frame_duration()" function), we effectively calculate the
transmission time as
SIFS + contentionWindow + dataTime + SIFS + ackTime
So why there are two SIFS???
Any idea?
--
regards;
Peizhao
reply other threads:[~2011-04-11 23:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DA38D97.1030407@gmail.com \
--to=peizhao.research@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=yinwei@itee.uq.edu.au \
/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.