From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
Johannes Berg <johannes@sipsolutions.net>,
Christian Lamparter <chunkeey@googlemail.com>,
linux-wireless@vger.kernel.org, linville@tuxdriver.com,
mathias.kretschmer@fokus.fraunhofer.de,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCH] nl80211: allow ad-hoc to set WMM parameters from outside
Date: Wed, 9 Jan 2013 14:15:40 +0100 [thread overview]
Message-ID: <20130109131540.GA22836@pandem0nium> (raw)
In-Reply-To: <CAJ-Vmom91BS5fPas+FWsaqQwm-ZVcZckUXB2vQgoEXtKiOH6mA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
On Tue, Jan 08, 2013 at 09:28:44AM -0800, Adrian Chadd wrote:
> I still populate the WME fields; I need to "fix" paying attention to
> them in the adhoc case.
Applying the EDCA parameters in the hardware and sending "standard" WME IEs
(without EDCA parameter sets) is understandable, Linux does that too.
But are you really sending EDCA parameters in IBSS mode within the WME IEs?
After all, STAs in infrastructure don't do this either.
>
> The performance loss without them is quite noticable.
I don't understand why. If you apply the default EDCA parameters/QoS parameters
in the hardware, it shouldn't make a difference if you transmit EDCA parameters
in your beacons or not. I'm confused. :)
Cheers,
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-01-09 13:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 18:50 [PATCH] Allow to set WMM parameters in IBSS mode Simon Wunderlich
2012-11-27 18:50 ` [PATCH] nl80211: allow ad-hoc to set WMM parameters from outside Simon Wunderlich
2012-11-28 14:01 ` Johannes Berg
2012-11-30 13:43 ` Simon Wunderlich
2012-12-28 15:05 ` Johannes Berg
2012-12-30 23:33 ` Simon Wunderlich
2013-01-01 23:46 ` Adrian Chadd
2013-01-02 12:58 ` Johannes Berg
2013-01-02 13:36 ` Christian Lamparter
2013-01-02 14:41 ` Johannes Berg
2013-01-08 14:13 ` Simon Wunderlich
2013-01-08 17:28 ` Adrian Chadd
2013-01-09 13:15 ` Simon Wunderlich [this message]
2013-01-09 14:10 ` Christian Lamparter
2013-01-09 14:33 ` Simon Wunderlich
2013-01-09 20:01 ` Christian Lamparter
2012-11-27 18:50 ` [PATCH] iw: allow to set wmm parameters from iw Simon Wunderlich
2012-11-27 21:14 ` [PATCHv2] " Simon Wunderlich
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=20130109131540.GA22836@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=adrian@freebsd.org \
--cc=chunkeey@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=siwu@hrz.tu-chemnitz.de \
/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