Lets make wifi fast again!
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "David Lang" <david@lang.hm>
Cc: "Bob McMahon" <bob.mcmahon@broadcom.com>,
	make-wifi-fast@lists.bufferbloat.net,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] more well funded attempts showing market demand for better wifi
Date: Thu, 23 Jun 2016 17:08:50 -0400 (EDT)	[thread overview]
Message-ID: <1466716130.728219772@apps.rackspace.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1606231350030.2044@nftneq.ynat.uz>





On Thursday, June 23, 2016 4:52pm, "David Lang" <david@lang.hm> said:

> On Thu, 23 Jun 2016, dpreed@reed.com wrote:
> 
>> The actual issues of transmitting on multiple channels at the same time are
>> quite minor if you do the work in the digital domain (pre-DAC).  You just need
>> a higher sampling rate in the DAC and add the two signals together (and use a
>> wideband filter that covers all the channels).  No RF problem.
> 
> that works if you are using channels that are close together, and is how the
> current standard wide channels in N and AC work.
> 
> If you try to use channels that aren't adjacent, this is much harder to do.
>
The whole 5 GHz U-NII band is not that wide.  It's easy to find DACs that run at 1 Gsps or better. On transmission you don't need to filter the bands where you put no energy in the middle (or not much).
 
> Remember that the current adjacent channel use goes up to 160MHz wide, going
> wider than that starts getting hard.
> 
>> Receiving multiple transmissions in different channels is pretty much the same
>> problem - just digitize (ADC) a wider bandwidth and separate in the digital
>> domain.  the only real issue on receive is equalization - if you receive two
>> different signals at different receive signal strengths, the lower strength
>> signal won't get as much dynamic range in its samples.
>>
>> But in a LAN setup, the variability in signal strength is likely small enough
>> that you can cover that with more ADC bits (or have the MAC protocol manage
>> the station transmit power so that signals received at the AP are nearly the
>> same power.
>>
>> Equalization at transmit works very well when there is a central AP (as in
>> cellular or normal WiFi systems).
> 
> define 'normal WiFi system'
Ones based on access points. In general, in typical WiFi deployments one prefers to make smaller cells so that the signal level variation between "near" and "far" signals is modest, which makes equalization much easier or even optional. If there is a large variation of power received at the access point then CSMA is hard to achieve, and the far stations have to run at slow rates, occupying more than their fair share of airtime.
(a non-normal system would be a peer-to-peer mesh over a wide enough area that you end up with "hidden terminal" issues all over the place)
> 
> It's getting very common for even moderate size houses to need more than one AP
> to cover the entire house.
> 
Agree. No question about that.


  reply	other threads:[~2016-06-23 21:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 17:03 Dave Taht
2016-06-22 17:18 ` Dave Taht
2016-06-22 18:08   ` Dave Taht
2016-06-23 19:55   ` Bob McMahon
2016-06-23 20:10     ` David Lang
2016-06-23 20:28       ` Bob McMahon
2016-06-23 20:35         ` David Lang
2016-06-23 20:48         ` dpreed
2016-06-23 20:52           ` David Lang
2016-06-23 21:08             ` dpreed [this message]
2016-06-23 21:41           ` Bob McMahon
2016-06-24  2:14             ` David Lang
2016-06-24  3:01               ` Bob McMahon
2016-06-24  5:19                 ` David Lang

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

  List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1466716130.728219772@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=bob.mcmahon@broadcom.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    /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