General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: erik.taraldsen@telenor.com
Cc: dave@taht.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] emulating non-duplex media in linux qdiscs
Date: Tue, 10 Oct 2017 09:21:19 -0400	[thread overview]
Message-ID: <16882.1507641679@obiwan.sandelman.ca> (raw)
In-Reply-To: <1507624730253.7735@telenor.com>

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


<erik.taraldsen@telenor.com> wrote:
    >> 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.

    > Well, as Mikael stated as well, half duplex has been used on shared
    > medium in the ethernet world since it's inception.  As you state it
    > does not match 100% with the wikipedia definition, but the tradition is
    > there.

The ethernet interface on the device is half-duplex, because it can only do tx
or rx to/from the coax cable.  There is in essence a half-duplex connection
there. (And with thickernet, there was actually a p2p AUI cable...)

But, the coax cable is *not* half-duplex, because it has more than two
senders to multiplex, so it can't be "half" duplex.
And it's the coax that we actually want to similate, not the AUI cable.

    > Given your distaste for the term half duplex, and the coming advances
    > in .11ax which further confuses the issue, there may be a real need for
    > a better term.  How about starting with a description of the
    > transmission properties and making a set of terms?  Shared medium,
    > single sender, multiple recivers. (current mu-mimo wifi).  Shared
    > medium multiple sender, multiple receivers. (OFDMA 802.11ax if they get
    > it working).  Shared medium entails coordinated action.
    > Sender/receiver description also encapsulates that there is different
    > behavior in the different direction in the air.

semi-multiplex

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-10-10 13:21 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
2017-10-10  7:02     ` Mikael Abrahamsson
2017-10-10  8:38     ` erik.taraldsen
2017-10-10 13:21       ` Michael Richardson [this message]
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=16882.1507641679@obiwan.sandelman.ca \
    --to=mcr+ietf@sandelman.ca \
    --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