From: Ben Greear <greearb@candelatech.com> To: Johannes Berg <johannes@sipsolutions.net>, Ashok Raj Nagarajan <arnagara@codeaurora.org> Cc: Ashok Raj Nagarajan <arnagara@qti.qualcomm.com>, linux-wireless@vger.kernel.org, ath10k@lists.infradead.org Subject: Re: [PATCH 1/2] cfg80211: Add support to set tx power for a station associated Date: Mon, 01 Aug 2016 06:27:42 -0700 [thread overview] Message-ID: <579F4E4E.80103@candelatech.com> (raw) In-Reply-To: <1470043740.3389.10.camel@sipsolutions.net> On 08/01/2016 02:29 AM, Johannes Berg wrote: > >> Sure.. First use case will be to help with the problem of legacy >> client devices that roam across multiple APs. It is a classic >> enterprise Wi-Fi AP problem, often managed by a "network controller" >> unit that is connected to all the APs. >> The problem is how to handle seamless handoff of clients between >> multiple APs while maximizing the client throughput and minimizing >> disruption of IP application services like VoIP calls and video >> streaming. A legacy client will often hold onto an AP association, >> even down to 1 Mbps as it roams away. Instead, if the AP can >> recognise that the client RSSI (and therefore throughput) is poor, it >> can "drop" the Tx power significantly (just to that client) such that >> it forcesthe client to look for a better, closer, and therefore >> higher-throughputassociation. It would "give it a kick" without >> blacklisting it. It just needsto hold the power low for the small >> amount of time it takes to convince it to go away. > > Not sure that *works* since implementations may just compare beacon > signal strength and hold on to the AP based on that, but it does seem > like a reasonable use case. How is that better than just kicking the station deliberately and/or refusing to send frames to it at all? Thanks, Ben > > How would this interact with automatic adjustment though? > > johannes > > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com> To: Johannes Berg <johannes@sipsolutions.net>, Ashok Raj Nagarajan <arnagara@codeaurora.org> Cc: linux-wireless@vger.kernel.org, Ashok Raj Nagarajan <arnagara@qti.qualcomm.com>, ath10k@lists.infradead.org Subject: Re: [PATCH 1/2] cfg80211: Add support to set tx power for a station associated Date: Mon, 01 Aug 2016 06:27:42 -0700 [thread overview] Message-ID: <579F4E4E.80103@candelatech.com> (raw) In-Reply-To: <1470043740.3389.10.camel@sipsolutions.net> On 08/01/2016 02:29 AM, Johannes Berg wrote: > >> Sure.. First use case will be to help with the problem of legacy >> client devices that roam across multiple APs. It is a classic >> enterprise Wi-Fi AP problem, often managed by a "network controller" >> unit that is connected to all the APs. >> The problem is how to handle seamless handoff of clients between >> multiple APs while maximizing the client throughput and minimizing >> disruption of IP application services like VoIP calls and video >> streaming. A legacy client will often hold onto an AP association, >> even down to 1 Mbps as it roams away. Instead, if the AP can >> recognise that the client RSSI (and therefore throughput) is poor, it >> can "drop" the Tx power significantly (just to that client) such that >> it forcesthe client to look for a better, closer, and therefore >> higher-throughputassociation. It would "give it a kick" without >> blacklisting it. It just needsto hold the power low for the small >> amount of time it takes to convince it to go away. > > Not sure that *works* since implementations may just compare beacon > signal strength and hold on to the AP based on that, but it does seem > like a reasonable use case. How is that better than just kicking the station deliberately and/or refusing to send frames to it at all? Thanks, Ben > > How would this interact with automatic adjustment though? > > johannes > > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-08-01 13:27 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-14 17:44 [PATCH 1/2] cfg80211: Add support to set tx power for a station associated Ashok Raj Nagarajan 2016-06-14 17:44 ` Ashok Raj Nagarajan 2016-06-28 10:48 ` Johannes Berg 2016-06-28 10:48 ` Johannes Berg 2016-07-05 12:31 ` Ashok Raj Nagarajan 2016-07-05 12:31 ` Ashok Raj Nagarajan 2016-08-01 9:29 ` Johannes Berg 2016-08-01 9:29 ` Johannes Berg 2016-08-01 13:27 ` Ben Greear [this message] 2016-08-01 13:27 ` Ben Greear 2016-11-07 14:10 ` Ashok Raj Nagarajan 2016-11-07 14:10 ` Ashok Raj Nagarajan 2016-11-07 14:18 ` Ben Greear 2016-11-07 14:18 ` Ben Greear 2016-11-15 9:31 ` Johannes Berg 2016-11-15 9:31 ` Johannes Berg
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=579F4E4E.80103@candelatech.com \ --to=greearb@candelatech.com \ --cc=arnagara@codeaurora.org \ --cc=arnagara@qti.qualcomm.com \ --cc=ath10k@lists.infradead.org \ --cc=johannes@sipsolutions.net \ --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: linkBe 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.