From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Can we increase IEEE80211_MAX_QUEUES
Date: Thu, 03 Dec 2015 21:24:05 +0100 [thread overview]
Message-ID: <1449174245.31265.4.camel@sipsolutions.net> (raw)
In-Reply-To: <1449174081.31265.3.camel@sipsolutions.net> (sfid-20151203_212138_334045_9AA12B0C)
On Thu, 2015-12-03 at 21:21 +0100, Johannes Berg wrote:
>
> Does the original premise even make sense though? A single queue for
> each vdev seems a bit strange.
>
Btw, it might make more sense to use Felix's txq scheduling thing for
this, where you get a txq for each station. You can still combine them
back any way you want in the driver.
johannes
next prev parent reply other threads:[~2015-12-03 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 20:16 Can we increase IEEE80211_MAX_QUEUES Ben Greear
2015-12-03 20:21 ` Johannes Berg
2015-12-03 20:24 ` Johannes Berg [this message]
2015-12-03 20:29 ` Ben Greear
2015-12-03 23:12 ` Ben Greear
2015-12-05 13:22 ` Michal Kazior
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=1449174245.31265.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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 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).