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:21:21 +0100 [thread overview]
Message-ID: <1449174081.31265.3.camel@sipsolutions.net> (raw)
In-Reply-To: <5660A31E.3010507@candelatech.com> (sfid-20151203_211637_306021_AF98F120)
On Thu, 2015-12-03 at 12:16 -0800, Ben Greear wrote:
> ath10k wants to use vdev-id as a queue-id, and I want to support up
> to
> 64 vdevs. In the 4.2 kernel, this is causing splats when using lots
> of
> vdevs because then queue is out of range.
>
> Can we just increase IEEE80211_MAX_QUEUES to 64?
>
I think not, that would likely cause a lot of data structures to grow
too much. We'd have to do more dynamic things in that case, I suppose.
Does the original premise even make sense though? A single queue for
each vdev seems a bit strange.
johannes
next prev parent reply other threads:[~2015-12-03 20:21 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 [this message]
2015-12-03 20:24 ` Johannes Berg
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=1449174081.31265.3.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 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.