From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] SIGCOMM MIT paper: Starvation in e2e congestion control
Date: Fri, 12 Aug 2022 08:22:24 +1200 [thread overview]
Message-ID: <3c1a8349-3877-644c-93d5-ed0b29c4ef92@auckland.ac.nz> (raw)
In-Reply-To: <1660246489.6578887@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 3070 bytes --]
On 12/08/2022 7:34 am, David P. Reed via Starlink wrote:
>
> I'll give you another example of a serious misuse of a theorem outside
> its range of applicability:
>
> Shannon proved a channel capacity theorem: C = W log(S / N). The proof
> is mathematical, and correct.
>
Indeed.
>
> But hiding in the assumptions are some very strong and rarely
> applicable conditions. It was a very useful result in founding
> information theory.
>
> But... it is now called "Shannon's Law" and asserted to be true and
> applicable to ALL communications systems.
>
...and it is. But it needs to be applied correctly.
>
> This turns out not to be correct. And it is hardly ever correct in
> practice.
>
Ahem ... if it's proven, it's correct, even in practice ;-)
>
> An example of non-correct application turns out to be when multiple
> transmissions of electromagnetic waves occur at the same time. EE
> practice is to treat "all other signals" as Gaussian Noise. They are
> not - they never are
>
Therein lies the problem. Correct theorem, incorrectly applied.
>
> .
>
> So, later information theorists discovered that where there are
> multiple signals received by a single receiving antenna, and only a
> little noise (usually from the RF Front End of the receiver, not the
> environment) the Slepian-Wolf capacity theorem applies C = W
> log(\sum(S[i]. i=1,N) /W).
>
Note: N here isn't the noise power (just the number of signals).
>
> That's a LOT more capacity than Shannon's Law predicts, especially in
> narrowband signalling.
>
Only if you lump in correlated signals with noise, which is an incorrect
(or rather, over-simplified) application of the Shannon-Hartley theorem.
>
> And noise itself is actually "measurement error" at the receiver,
> which is rarely Gaussian, in fact it really is quite predictable
> and/or removable.
>
Noise in the Shannon sense is random and therefore not predictable or
correlated. Interference can be both predictable and correlated, and
therefore can sometimes be removed / to an extent. Modelling
interference as noise means not exploiting its inherent properties, and
yes that means ending lower capacity. But that doesn't mean that either
theorem is inapplicable - Shannon's fundamental limit still holds, even
in the multi-user case, as long as the noise you plug in is the "little
noise" from the RF front end and leave the interference out.
The point I guess is that models are just models, and the more you know
about what it is that you are dealing with, the better you can model.
Which, I suppose, applies to managing queues also. The more you know
what's in them and how it'll respond when you manage it, the better.
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
[-- Attachment #2: Type: text/html, Size: 7370 bytes --]
next prev parent reply other threads:[~2022-08-11 20:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.562.1660228174.1281.starlink@lists.bufferbloat.net>
2022-08-11 19:34 ` David P. Reed
2022-08-11 20:22 ` Ulrich Speidel [this message]
2022-08-11 20:24 ` Ulrich Speidel
2022-08-12 14:21 ` Livingood, Jason
2022-08-12 14:23 ` Hesham ElBakoury
2022-08-25 20:26 ` Dave Taht
[not found] <mailman.3.1659715201.24001.starlink@lists.bufferbloat.net>
2022-08-08 21:39 ` David P. Reed
2022-08-08 22:37 ` David Lang
2022-08-08 22:41 ` Dave Taht
2022-08-11 14:29 ` Hesham ElBakoury
2022-08-17 21:34 ` Dave Taht
2022-08-04 19:05 Dave Taht
2022-08-07 4:28 ` Venkat Arun
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c1a8349-3877-644c-93d5-ed0b29c4ef92@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--cc=starlink@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