General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Andrew Shewmaker <agshew@gmail.com>
To: Dave Taht <dave@taht.net>
Cc: erik.taraldsen@telenor.com, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] emulating non-duplex media in linux qdiscs
Date: Mon, 9 Oct 2017 13:05:03 -0600	[thread overview]
Message-ID: <CAF-E8XFU8sDJnWLzSA20JN404q=WKAJwic2ovK3vVG5iQUMjUA@mail.gmail.com> (raw)
In-Reply-To: <87376s6z5z.fsf@nemesis.taht.net>

[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]

On Mon, Oct 9, 2017 at 10:53 AM, Dave Taht <dave@taht.net> wrote:
>
> <erik.taraldsen@telenor.com> writes:
>
> > Half duplex is the term you are looking for
> > https://en.wikipedia.org/wiki/Duplex_(telecommunications)
>
> "A duplex communication system is a point-to-point system composed
> of two connected parties or devices that can communicate with one
> another in both directions."
>
> wifi is not p2p, all data is broadcast to many potential recievers,
> only one can transmit at one time.
>
> Saying that is half duplex, doesn't work for me. In their example of
> "half duplex", (using push to talk), it still means that everybody on
> that channel hears who is talking. "half duplex" to me, given the
> definition of duplex, means more that there is a *p2p* channel (a wire),
> that you can ping pong data across.
>
> This conflation of ideas has always bugged me and I've longed to find
> another word that more accurately describes what happens, therefore
> I've been saying "non-duplex".

Isn't wi-fi adequately described as a combination of frequency and time
domain multiplexing? In my mind, "multiplex" would be better than "
non-duplex", since using the latter could reasonably be interpreted as
"anything not duplex".




--
Andrew Shewmaker

[-- Attachment #2: Type: text/html, Size: 1999 bytes --]

  reply	other threads:[~2017-10-09 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09  1:54 Dave Taht
2017-10-09  7:41 ` erik.taraldsen
2017-10-09 16:53   ` Dave Taht
2017-10-09 19:05     ` Andrew Shewmaker [this message]
2017-10-10  7:02     ` Mikael Abrahamsson
2017-10-10  8:38     ` erik.taraldsen
2017-10-10 13:21       ` Michael Richardson
2017-10-09 13:09 ` Y
2017-10-09 20:21 ` Stephen Hemminger
2017-10-09 21:04 ` Michael Richardson
2017-10-10  9:25 ` Luca Muscariello

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='CAF-E8XFU8sDJnWLzSA20JN404q=WKAJwic2ovK3vVG5iQUMjUA@mail.gmail.com' \
    --to=agshew@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave@taht.net \
    --cc=erik.taraldsen@telenor.com \
    /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