From: sylvain_gmail <sylvain.roger.rieunier@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: nbd@openwrt.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] minstrel_ht: enable frame aggregation for fixed rate
Date: Tue, 12 Jun 2012 12:42:23 +0200 [thread overview]
Message-ID: <4FD71D0F.2080101@gmail.com> (raw)
In-Reply-To: <1339426690.4520.28.camel@jlt3.sipsolutions.net>
Dear Johannes ans Felix,
This is my new change log version :
"This patch adds frame aggregation for fixed rate mode through debugfs.
Instead of using sample_idx, which set IEEE80211_TX_CTL_RATE_CTRL_PROBE
flag,
which disabled frame aggregation, we set max_tp_rate and max_tp_rate2 which
do not disable frame aggregation."
What's is your opinion?
Sylvain
Le 11/06/2012 16:58, Johannes Berg a écrit :
> On Mon, 2012-06-11 at 16:51 +0200, sylvain_gmail wrote:
>> Dear Johannes and Felix ,
>>
>> Here is the description of my patch that I can offer :
>>
>> "After trying to fix rate control with minstrel_ht. I realized that,
>> that fix rate was not allowed to make frames aggregation.
>> This was due to enable IEEE80211_TX_CTL_RATE_CTRL_PROBE flag of the
>> ieee80211_tx_info structure.
>> Because when IEEE80211_TX_CTL_RATE_CTRL_PROBE flag is set frame
>> aggregation is disabled.
>> So instead of used sample_idx, who set
>> IEEE80211_TX_CTL_RATE_CTRL_PROBE flag. I suggest using max_tp_rate and
>> max_tp_rate2 which do not disabled frame aggregation."
>>
>> what is your opinion?
> Makes more sense than before, but isn't really a viable changelog entry
> yet :)
>
> johannes
>
prev parent reply other threads:[~2012-06-12 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 7:44 [PATCH v2] minstrel_ht: enable frame aggregation for fixed rate Sylvain Roger Rieunier
2012-06-09 8:10 ` Johannes Berg
[not found] ` <4FD605DD.9020800@gmail.com>
2012-06-11 14:58 ` Johannes Berg
2012-06-12 10:42 ` sylvain_gmail [this message]
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=4FD71D0F.2080101@gmail.com \
--to=sylvain.roger.rieunier@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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.