From: "John W. Linville" <linville@tuxdriver.com>
To: Joerg Pommnitz <pommnitz@yahoo.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 802.11: Throughput optimization beyond rate selection
Date: Mon, 12 Oct 2009 09:59:49 -0400 [thread overview]
Message-ID: <20091012135949.GD27575@tuxdriver.com> (raw)
In-Reply-To: <487238.22616.qm@web51405.mail.re2.yahoo.com>
On Mon, Oct 12, 2009 at 02:28:07AM -0700, Joerg Pommnitz wrote:
> Hello all,
> the throughput achieved over a wireless 802.11 network depends on more than the
> rate selection. Other parameters are fragmentation threshold, RTS threshold
> and the retry limits. Are you aware of a "unified throughput optimization" algorithm
> that tries to optimize the whole parameter set instead of just the data rate?
No, do tell...post code as well... :-)
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-10-12 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 9:28 802.11: Throughput optimization beyond rate selection Joerg Pommnitz
2009-10-12 13:59 ` John W. Linville [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=20091012135949.GD27575@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pommnitz@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).