From: Daniel Drake <dsd@gentoo.org>
To: Ulrich Kunitz <kune@deine-taler.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
softmac-dev@sipsolutions.net, netdev@vger.kernel.org
Subject: Re: [PATCH][RFC] softmac: suggest TX rate
Date: Mon, 17 Apr 2006 02:02:24 +0100 [thread overview]
Message-ID: <4442E920.60603@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0604170235020.32457@p15091797.pureserver.info>
Ulrich Kunitz wrote:
> I just wanted to say, I agree with the approach, but wonder how
> transmission timeouts come into play here, which should lead to a
> decrease of the tranmission rate.
That's a separate issue, to do with rate management, which I'm not
tackling yet. Note that the functions in my patch can easily be extended
to bring rate management into the equation.
Daniel
next prev parent reply other threads:[~2006-04-17 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 0:28 [PATCH][RFC] softmac: suggest TX rate Daniel Drake
2006-04-17 0:33 ` Ulrich Kunitz
2006-04-17 0:40 ` Ulrich Kunitz
2006-04-17 1:02 ` Daniel Drake [this message]
2006-04-17 9:16 ` Johannes Berg
2006-04-17 17:43 ` Daniel Drake
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=4442E920.60603@gentoo.org \
--to=dsd@gentoo.org \
--cc=johannes@sipsolutions.net \
--cc=kune@deine-taler.de \
--cc=netdev@vger.kernel.org \
--cc=softmac-dev@sipsolutions.net \
/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).