General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jan Ceuleers <jan.ceuleers@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Cerowrt-devel] uplink bufferbloat and scheduling problems
Date: Thu, 2 Dec 2021 09:11:35 +0100	[thread overview]
Message-ID: <22dce828-cfd1-3092-ac28-7d0b0c0913c0@gmail.com> (raw)
In-Reply-To: <1638390391.091227727@apps.rackspace.com>

On 01/12/2021 21:26, David P. Reed wrote:
> In any CSMA link (WiFi), there is no "up" or "down". There is only
> sender and receiver, and each station and the AP are always doing both.

Generally though the silicon used in WiFi APs is much more capable than
that used in STAs. The capabilities of (particularly STA-side) silicon
are different as they relate to uplink and downlink.

Of course for a given AP-STA link a common subset of capabilities needs
to be used, but that subset might be different in either direction.

The antennas (number and gain), receiver sensitivity and transmit power
are also different.

A simple example of a reason why uplink and downlink might be different:
the achievable bitrate on the AP-to-STA downlink might be higher than
the uplink because the AP's transmit power is higher. In order to be
able to achieve the same bitrate if the STA's transmit power is lower
the AP's receiver sensitivity would have to be that much better.

Generalising to other shared-media technologies: whenever the UL/DL link
budgets are different the link is going to by asymmetric.

Jan

  parent reply	other threads:[~2021-12-02  8:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01  0:13 [Bloat] " Dave Taht
2021-12-01 20:26 ` [Bloat] [Cerowrt-devel] " David P. Reed
2021-12-01 21:06   ` David Lang
2021-12-01 21:09   ` David Lang
2021-12-01 22:28     ` Valdis Klētnieks
2021-12-02  0:10       ` Toke Høiland-Jørgensen
2021-12-02  9:09         ` David Lang
2021-12-02 17:20     ` Dave Collier-Brown
2021-12-02 19:33       ` David Lang
2021-12-02  8:11   ` Jan Ceuleers [this message]
2021-12-02  8:45   ` Sebastian Moeller

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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=22dce828-cfd1-3092-ac28-7d0b0c0913c0@gmail.com \
    --to=jan.ceuleers@gmail.com \
    --cc=bloat@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