From: Johannes Berg <johannes@sipsolutions.net>
To: Dmitry Shmidt <dimitrysh@google.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] RFC: Universal scan proposal
Date: Tue, 13 Dec 2016 17:04:31 +0100 [thread overview]
Message-ID: <1481645071.20412.30.camel@sipsolutions.net> (raw)
In-Reply-To: <CAH7ZN-wP+9AGrXFUS4RY65-RyfP-J46svBvLdytP2c=QPtiaug@mail.gmail.com> (sfid-20161207_193938_431091_4D11FB31)
> > Well eventually we also have to clear for location if we run out of
> > memory, that usually means dumping them out to the host, no?
>
> Being out of memory and consuming more memory are different
> things, but I agree - maybe we don't need to worry about it.
Well, reaching the limit of what we're willing to spend on it is
equivalent I guess :)
> > I'm not entirely sure about this case - surely noticing "we can do
> > better now" is still better than waiting for being able to make the
> > perfect decision?
>
> Maybe we can just keep flag saying that currently available results
> were not received by usual full scan.
Elsewhere we were planning per-channel results, and a cookie to filter
them - perhaps we could have a similar thing where you may even have to
request these scan results specifically with a certain cookie you got
from the scanning, or so. Or indicate the cookie there so you can tie
it back to the scan request somehow?
> So, let's summarize:
> Instead of creating new type of generic scan with special types,
> we want to go with additional expansion of scheduled scan options and
> parameters (in order not to "multiply entities"), including ability
> to send new scheduled scan request without stopping previous one.
>
> Is it Ok?
Sounds fine to me.
johannes
next prev parent reply other threads:[~2016-12-13 16:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 22:47 [PATCH] RFC: Universal scan proposal dimitrysh
2016-11-17 20:56 ` Arend Van Spriel
2016-11-18 23:53 ` Dmitry Shmidt
2016-11-22 7:24 ` Luca Coelho
2016-11-22 17:29 ` Dmitry Shmidt
2016-11-22 20:41 ` Arend Van Spriel
2016-11-22 20:54 ` Dmitry Shmidt
2016-11-23 8:43 ` Arend Van Spriel
2016-11-28 19:25 ` Dmitry Shmidt
2016-12-05 14:28 ` Johannes Berg
2016-12-05 18:32 ` Dmitry Shmidt
2016-12-07 6:44 ` Johannes Berg
2016-12-07 18:39 ` Dmitry Shmidt
2016-12-07 20:51 ` Arend Van Spriel
2016-12-08 22:35 ` Dmitry Shmidt
2016-12-09 11:10 ` Arend Van Spriel
2016-12-13 16:06 ` Johannes Berg
2017-01-03 20:45 ` Dmitry Shmidt
2017-01-04 13:28 ` Johannes Berg
2017-01-04 20:32 ` Dmitry Shmidt
2017-01-05 11:46 ` Johannes Berg
2017-01-05 13:39 ` Arend Van Spriel
2017-01-05 13:44 ` Johannes Berg
2017-01-05 19:59 ` Arend Van Spriel
2017-01-09 10:48 ` Johannes Berg
2017-01-09 12:07 ` Arend Van Spriel
2017-01-11 13:14 ` Johannes Berg
2017-01-05 20:45 ` Dmitry Shmidt
2017-01-09 10:45 ` Johannes Berg
2017-01-09 11:19 ` Arend Van Spriel
2016-12-13 16:04 ` Johannes Berg [this message]
2016-12-21 10:20 ` [RFC] nl80211: allow multiple active scheduled scan requests Arend van Spriel
2017-01-02 10:44 ` Johannes Berg
2017-01-03 12:25 ` Arend Van Spriel
2017-01-04 9:59 ` Johannes Berg
2017-01-04 10:20 ` Arend Van Spriel
2017-01-04 10:30 ` Johannes Berg
2017-01-04 10:34 ` Arend Van Spriel
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=1481645071.20412.30.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dimitrysh@google.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).