From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "greearb@candelatech.com" <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath9k-devel@venema.h4ckr.net" <ath9k-devel@venema.h4ckr.net>
Subject: Re: [ath9k-devel] [PATCH v2 3/3] ath9k: Keep track of stations for debugfs.
Date: Sun, 09 Jan 2011 10:33:13 +0100 [thread overview]
Message-ID: <1294565593.3469.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20110107201204.GG21588@tux>
On Fri, 2011-01-07 at 12:12 -0800, Luis R. Rodriguez wrote:
> On Thu, Jan 06, 2011 at 08:49:12PM -0800, greearb@candelatech.com wrote:
> > From: Ben Greear <greearb@candelatech.com>
> >
> > The stations hold the ath_node, which holds the tid
> > and other xmit logic structures. In order to debug
> > stuck xmit logic, we need a way to print out the tid
> > state for the stations.
> >
> > Signed-off-by: Ben Greear <greearb@candelatech.com>
> > ---
> >
> > v1 -> v2: Use linked list instead of array. Protect with spinlock.
>
> Again, see my comments about the # STAs limit. I think this can go in
> as a cfg80211 driver limitation which can be exposed.
There's a todo list item that is more generic -- exposing the possible
interface combinations including their counts. So if anything, we should
start working on that, although I agree that if the limit is just due to
bugs, it shouldn't be advertised.
johannes
prev parent reply other threads:[~2011-01-09 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 4:49 [PATCH v2 3/3] ath9k: Keep track of stations for debugfs greearb
2011-01-07 20:12 ` [ath9k-devel] " Luis R. Rodriguez
2011-01-07 20:24 ` Ben Greear
2011-01-07 23:24 ` Felix Fietkau
2011-01-09 9:33 ` Johannes Berg [this message]
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=1294565593.3469.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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).