linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 00/12] multi-channel support
Date: Tue, 27 Mar 2012 13:59:28 +0200	[thread overview]
Message-ID: <1332849568.3938.7.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4F71A7AE.3050405@tieto.com>

On Tue, 2012-03-27 at 13:42 +0200, Michal Kazior wrote:

> >> But how do we then check if we need to stop given queue or not? Let's
> >> say a driver stops q=2 which corresponds to BE on vif0 and vif1. But
> >> then comes mac80211 aggregation and stops BE on vif0. I can only think
> >> of a single solution to that: "u8 lock_reasons[256];" in ieee80211_local
> >> but it seems like an overkill or is it not?
> >
> > Essentially that's what I was considering, we'd maintain all the queue
> > state per HW queue ID. I said it would be a u8 for the HW queue ID, but
> > I don't see anyone using more than say 32 or so, so we wouldn't really
> > need 256. But we could go up to 256 if needed (though at that point we
> > should probably do dynamic allocation instead.)
> 
> We could maybe allocate it according to hw.queues? I think it should be 
> okay unless a driver has some kind of non-static queues. Are you aware 
> of such a device/driver?

Yeah, we could do that. I'm not sure I want the complexity though, if
the limit is going to be something like 16 (I said 32 before but now
think for our current use 16 would be sufficient) I don't see much value
in dynamically allocating over just reserving space for 16.

johannes


  reply	other threads:[~2012-03-27 11:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 12:21 [RFC 00/12] multi-channel support Michal Kazior
2012-03-23  9:29 ` Johannes Berg
2012-03-23 14:03   ` Michał Kazior
2012-03-23 14:31     ` Johannes Berg
2012-03-26 12:27       ` Michal Kazior
2012-03-26 12:45         ` Johannes Berg
2012-03-27 11:42           ` Michal Kazior
2012-03-27 11:59             ` Johannes Berg [this message]
2012-03-23 15:01     ` Johannes Berg
2012-03-23 15:06       ` Johannes Berg
2012-03-26 12:29       ` Michal Kazior
2012-03-26 13:19         ` Johannes Berg
2012-03-27 14:41           ` Michal Kazior
2012-03-27 15:00             ` Johannes Berg
2012-03-28  6:12               ` 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=1332849568.3938.7.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.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).