From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Add option to have more than one process listen for beacons per wiphy?
Date: Tue, 23 Oct 2012 09:23:15 +0200 [thread overview]
Message-ID: <1350976995.10322.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5085DB66.7020400@candelatech.com> (sfid-20121023_014858_488231_EE4955D4)
On Mon, 2012-10-22 at 16:48 -0700, Ben Greear wrote:
> A simple means would be a fixed-length array of nlpids (with max of maybe
> 16 or so). Or, could do a variable length array, or list, or some other
> way to register more than one at a time. If it were up to me, I'd choose
> a fixed-length array just to keep the code simple.
>
> Any opinions on this?
Fixed-length seems like a bad idea, you'll eventually complain about it
again :P
A list of small structures like the management frame registrations seems
like the best option?
Alternatively, we could have a new multicast group but that'd also
require hostapd changes.
johannes
prev parent reply other threads:[~2012-10-23 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 23:48 Add option to have more than one process listen for beacons per wiphy? Ben Greear
2012-10-23 7:23 ` 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=1350976995.10322.2.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 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.