From: Johannes Berg <johannes@sipsolutions.net>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4] mac80211: Optimize sta lookup for many VIFs
Date: Tue, 09 Apr 2013 11:50:48 +0200 [thread overview]
Message-ID: <1365501048.8465.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1364572823-28071-1-git-send-email-greearb@candelatech.com> (sfid-20130329_170033_026763_9F6C74DD)
On Fri, 2013-03-29 at 09:00 -0700, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> The sta_info hash is designed to deal with an AP
> with lots of stations associated, or a station interface
> connected to a single AP.
Given your other hash patches, does this even make sense still?
johannes
next prev parent reply other threads:[~2013-04-09 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 16:00 [PATCH v4] mac80211: Optimize sta lookup for many VIFs greearb
2013-04-03 12:58 ` Johannes Berg
2013-04-03 13:18 ` Ben Greear
2013-04-03 13:19 ` Johannes Berg
2013-04-09 9:50 ` Johannes Berg [this message]
2013-04-09 17:35 ` Ben Greear
2013-04-11 9:15 ` Johannes Berg
2013-04-11 16:17 ` Ben Greear
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=1365501048.8465.13.camel@jlt4.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).