From: Dennis Borgmann <dennis.borgmann@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Disabling ACKs with ath5k
Date: Fri, 25 Mar 2011 14:42:31 +0100 [thread overview]
Message-ID: <4D8C9BC7.3090204@googlemail.com> (raw)
In-Reply-To: <20110325131957.GA2242@tuxdriver.com>
Hello John,
the goal would be to have a transmission as fast as possible while
ignoring, if a packet reached its destination or not. I'd like to test
wireless performance regarding transmission time in a dedicated
environment. As far as I can see, backoff might already push the
transmission times up quite a lot and if I'd even add the time of -
worst case - 10 retransmissions, the transmission time of one packet
will grow even more.
It would be second-rank, if the packet reaches its destination. Loss of
some packets is not a problem in my testbed.
So I'd like to disable usage of ACKs in order to be off with the only
problem - backoff. Disabling this would of course be nice, but I fear,
that's far more work that just disabling ACKs.
Dennis
John W. Linville schrieb:
> On Fri, Mar 25, 2011 at 08:42:28AM +0100, Dennis Borgmann wrote:
>
>
>> Is there an interface to disable transmission of ACKs and on the other
>> hand ignoring unreceived ACKs. It can be done with multicasting, but can
>> it also be achieved by a setting with non-multicast-traffic? I am using
>> ath5k.
>>
>
> I'm curious, why do you want to do that?
>
>
next prev parent reply other threads:[~2011-03-25 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 7:42 Disabling ACKs with ath5k Dennis Borgmann
2011-03-25 13:19 ` John W. Linville
2011-03-25 13:42 ` Dennis Borgmann [this message]
2011-03-25 17:06 ` Nick Kossifidis
[not found] ` <BANLkTi=+nCfSj=3w2i-TUr1zawLfvm3Xog@mail.gmail.com>
2011-03-27 19:40 ` Dennis Borgmann
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=4D8C9BC7.3090204@googlemail.com \
--to=dennis.borgmann@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).