The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Donner <marc.donner@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] is networking different?
Date: Sun, 3 Jul 2022 16:32:06 -0400	[thread overview]
Message-ID: <CALQ0xCAX4LZALeVBvVK-D3szZTB9DU_G7cs__1S_tMbPjHPivA@mail.gmail.com> (raw)

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

On June 28 Rob Pike wrote:

"One of the reasons I'm not a networking expert may be relevant here. With
networks, I never found an abstraction to hang my hat on. Unlike with file
systems and files, or even Unix character devices, which provide a level of
remove from the underlying blocks and sectors and so on, the Unix
networking interface always seemed too low-level and fiddly, analogous to
making users write files by managing the blocks and sectors themselves."

I've been ruminating on the question of whether networks are different from
disks (and other devices).  Here are a couple of observations:

1 - Two different packets may take two different paths from the sender to
the receiver.

1a - The transit time for one packet may vary widely from that of the other.

1b - The two packets may arrive in an order different from the order in
which they were transmitted.

(Note - recently I have been reading Bob Gezelter's monograph [and PhD
dissertation] and I've learned that modern high-performance disk systems
behave more like networks in 1a and 1b.)

2 - A packet may never arrive.

3 - Behavior 2 not a sign of hard failure for networks, whereas it is
generally considered so for other I/O devices.

There is probably more to why networks are weird, but these are some of the
big dissonances that seem to me to make Rob's comment resonate so loudly to
me.

Best,

Marc
=====
nygeek.net
mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>

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

             reply	other threads:[~2022-07-03 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03 20:32 Marc Donner [this message]
2022-07-03 20:34 ` [TUHS] " Marc Donner
2022-07-03 20:57 ` Dan Stromberg
2022-07-03 21:55   ` Richard Salz

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

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

  git send-email \
    --in-reply-to=CALQ0xCAX4LZALeVBvVK-D3szZTB9DU_G7cs__1S_tMbPjHPivA@mail.gmail.com \
    --to=marc.donner@gmail.com \
    --cc=tuhs@tuhs.org \
    /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;
as well as URLs for NNTP newsgroup(s).