From: Daniel Drake <dsd@gentoo.org>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Michael Buesch <mb@bu3sch.de>,
Ulrich Kunitz <kune@deine-taler.de>,
John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: zd-mac80211: Fix TX status reports.
Date: Tue, 11 Sep 2007 08:52:21 +0100 [thread overview]
Message-ID: <46E64935.9010905@gentoo.org> (raw)
In-Reply-To: <1ba2fa240709102050l75402df4w19ef746d6243dbab@mail.gmail.com>
Tomas Winkler wrote:
> Receiving all ACKs packets will degraded performance greatly for sure,
> even on PCI interface.
> Receving ACK can maybe allowed selectively only for management packets
> including EAPOLS in some synchronous way, yet this is still error
> prone.
I don't think we have such control. It's either all ACKs or no ACKs.
> It looks strange to me that there is no other HW mechanism that does that?
> Is this driver reverse engineered?
No. There is another mechanism for detecting failed transmissions: we
get an interrupt for every failed TX. I feel that this should be enough
to implement rate control, however mac80211 at the moment requires
reports of both success and failure for rate control to work. Detecting
success is the tricky part.
Daniel
next prev parent reply other threads:[~2007-09-11 7:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 21:41 zd-mac80211: Fix TX status reports Michael Buesch
2007-09-09 10:05 ` Ulrich Kunitz
2007-09-09 10:58 ` Michael Buesch
2007-09-10 10:52 ` Johannes Berg
2007-09-10 10:58 ` Michael Buesch
2007-09-10 11:10 ` Johannes Berg
2007-09-11 3:50 ` Tomas Winkler
2007-09-11 7:52 ` Daniel Drake [this message]
2007-09-11 10:03 ` Tomas Winkler
2007-09-11 10:17 ` Johannes Berg
2007-09-11 10:20 ` Michael Buesch
2007-09-11 10:29 ` Johannes Berg
2007-09-11 10:52 ` Michael Buesch
2007-09-11 10:57 ` Johannes Berg
2007-09-11 22:32 ` Ulrich Kunitz
2007-09-12 8:40 ` Tomas Winkler
2007-09-12 8:54 ` Johannes Berg
2007-09-12 8:56 ` Johannes Berg
2007-09-13 5:56 ` Ulrich Kunitz
2007-09-13 7:15 ` Johannes Berg
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=46E64935.9010905@gentoo.org \
--to=dsd@gentoo.org \
--cc=johannes@sipsolutions.net \
--cc=kune@deine-taler.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=tomasw@gmail.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).