All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hubert Feurstein <h.feurstein@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] queue priority mapping
Date: Tue, 25 Nov 2014 22:14:00 +0100	[thread overview]
Message-ID: <CAFfN3gVtvw4o38PSD-4CMrkpsqaYC=9xSjGfWDa8BM3t+v3-gw@mail.gmail.com> (raw)
In-Reply-To: <5472F604.3020404@fami-braun.de>

Hi,

2014-11-24 10:10 GMT+01:00 M. Braun <michael-dev@fami-braun.de>:
[...]
>
> I don't know about the hw priority stuff, but the change you propose
> does not change the resulting data structure at all.
> You'd likely need to change mac80211_qnum to be IEEE80211_NUM_ACS-1-i
> (and maybe others) to change the mapping.

Well, in fact it does. To understand my post you have to know the
behaviour of ath_txq_setup. The point here is that on the first call
of ath_txq_setup(..ATH9K_TX_QUEUE_DATA..), hw-queue 0 is returned. On
the second call hw-queue 1 is returned, ... . And IEEE80211_AC_VO = 0,
so hw-queue 0 is assigned, which is wrong in my opinion. But the right
place to fix this would be ath_txq_setup itself.

Regards
Hubert

  reply	other threads:[~2014-11-25 21:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 18:00 [ath9k-devel] queue priority mapping Hubert Feurstein
2014-11-24  9:10 ` M. Braun
2014-11-25 21:14   ` Hubert Feurstein [this message]
2014-11-25 21:22     ` Dave Taht
2014-11-26  7:46     ` M. Braun
2014-11-26 12:25     ` Sujith Manoharan
2014-11-27 12:04       ` Hubert Feurstein
2014-11-30 11:30         ` Thomas Hühn
2014-11-30 18:18           ` Sergey Ryazanov
2014-11-30 21:57             ` Thomas Hühn
2014-11-30 22:11               ` Sergey Ryazanov

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='CAFfN3gVtvw4o38PSD-4CMrkpsqaYC=9xSjGfWDa8BM3t+v3-gw@mail.gmail.com' \
    --to=h.feurstein@gmail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.