Wow, 160-180 Mb/s. That's great :-)
No, it's HT40 but my AP is not very good, it sends to me only A-MSDUs but no
A-MPDUs (don't know why, i guess because it's cheap), and there are many
WLANs in my neighbourhood in 2.4GHZ and no WLANs in 5GHZ but unfortunately i
have an 2GHZ only AP. Furthermore,
That's great to hear. I take it this is HT20? I believe you can get
40-60 Mb/s @ MCS15 w/o AMPDU and 80-100 Mb/s w/ AMPDU. In HT40 I've
gotten 160-180 Mb/s for TCP netperf (5GHz) and 220+ Mb/s for
unidirectional streams (netperf -t UDP_STREAM). Note that once you get
to these higher rates t
Hi,
thanks for your help, I implemented A-MPDU Tx in my Ralink driver now and it
works very good.
I have average Tx rate about 4.5~5 MBytes/s now :-) The Ralink chip that i
have implements the frame queue in hardware so i had only to assign sequence
numbers, set BA window size and MPDU density and
Alexander Egorenkov wrote:
Why doesn't 802.11 stack assign sequence numbers to A-MPDU frames ?
Because if net80211 does the assignment it may be wrong. As the comment
says, if tx aggregation causes frames to be q'd above the h/w then by
the time they are sent OTA the pre-assigned seq# may be
No, ralink.
On Sun, Jan 31, 2010 at 3:12 PM, Rui Paulo wrote:
>
> On 27 Jan 2010, at 19:04, Alexander Egorenkov wrote:
>
> > Hi,
> >
> > i'm implementing a device driver for a 802.11n NIC under FreeBSD 8
>
> Just to make sure we don't step on each others shoes: it's not ath(4),
> right?
>
> --
>
And i took a look into the 802.11 stack of OpenSolaris which also supports
802.11n.
This 802.11n stack is very similar to the FreeBSD 802.11n stack and it
assigns sequence numbers to A-MPDU frames. I did it in my device driver like
802.11n stack from OpenSolaris does it.
See this link:
http://src
Why doesn't 802.11 stack assign sequence numbers to A-MPDU frames ?
When sequence numbers are not assigned to A-MPDU frames, then BA doesn't
work with my AP.
I tried to assign sequence numbers to A-MPDU frames in my device driver and
then BAs worked
with my AP.
And what is meant by aggregation queu
Alexander Egorenkov wrote:
Sorry, i posted the wrong comment.
Here is the comment which i don't understand:
/*
* NB: don't assign a sequence # to potential
* aggregates; we expect this happens at the
* point the frame comes off any aggregation q
Hi,
i'm implementing a device driver for a 802.11n NIC under FreeBSD 8
und experimented with A-MPDU transmission. I looked into net80211 code
and there is some code which implements this feature but it worked not very
well for me.
I noticed e.g. that sequence numbers are not assigned to A-MPDU fra
Sorry, i posted the wrong comment.
Here is the comment which i don't understand:
/*
* NB: don't assign a sequence # to potential
* aggregates; we expect this happens at the
* point the frame comes off any aggregation q
* as otherwise we may intro
10 matches
Mail list logo
