9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] datakit
Date: Thu, 19 Aug 2004 22:46:36 -0700	[thread overview]
Message-ID: <53811f0a56be6321b1fe11d35ee21d21@collyer.net> (raw)
In-Reply-To: <20040820130920.2a08bf59@garlic.apnic.net>

George commented:
> you can't take the checksums out of the IP/above layers because one
> sub-net claims to be reliable, so you wind up doing checksums in all
> layers (this wouldn't have only been true for IP btw.  links are not
> homogenous, so absent AT&T owning everywhere, if you want to talk
> everywhere you wind up having to do your own anyway)

Just to clarify, I'm unaware of any datakit/ip gateways (other than
multi-homed hosts, such as a Plan 9 cpu server (or two?) used to be).
So traffic within the world of datakit presumably could have lived
without upper-level checksums.  Looking at the second edition
port/stasync.c, it appears that CRCs were used in some cases.

To address the larger issue of trusting the network, that Ron raised,
I don't know how much intelligence was in a Datakit host interface,
but one could imagine end-to-end checksums or CRCs being handled by
the host interfaces (and probably between intermediate nodes too).
The better gigabit Ethernet cards offer to compute UDP and TCP
checksums incoming and outgoing for you, thus effectively pushing the
checksums and their verification very nearly into `the network' (your
network interface driver still has to check a bit that says `yup, the
checksums are okay'), at least within a single gigabit Ethernet.  Can
you trust these cards and your PCI buses to deliver your data
reliably?  Would you compute and verify the checksums in the IP stack
instead?  What about at 10Gb/s?



  reply	other threads:[~2004-08-20  5:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 15:11 Steve Simon
2004-08-20  1:35 ` geoff
2004-08-20  1:52   ` George Michaelson
2004-08-20  2:43     ` geoff
2004-08-20  3:09       ` George Michaelson
2004-08-20  5:46         ` geoff [this message]
2004-08-21  0:33           ` ron minnich
2004-08-21  4:51             ` boyd, rounin
2004-08-21 14:22             ` Brantley Coile
2004-08-22  9:50               ` Tim Newsham
2004-08-23  2:50               ` ron minnich
2004-08-20 14:13         ` boyd, rounin
2004-08-20  9:45       ` C H Forsyth
2004-08-20 12:55         ` Long Political Rant. Was: [Re: [9fans] datakit] Dave Lukes
2004-08-20 16:45           ` Jack Johnson
2004-08-20 16:59             ` rog
2004-08-20 13:06         ` [9fans] datakit Wes Kussmaul
2004-08-20 16:51         ` Skip Tavakkolian
2004-08-20 17:07           ` rog
2004-08-22 19:06             ` Jack Johnson
2004-08-20 18:41           ` boyd, rounin
2004-08-21 16:37             ` Boris Maryshev
2004-08-21 17:19             ` Boris Maryshev
2004-08-20  3:30     ` ron minnich
2004-08-20 14:24       ` boyd, rounin
2004-08-23 15:04         ` andrey mirtchovski
2004-08-23 15:27           ` ron minnich
2004-08-20 13:48   ` boyd, rounin
2004-08-20  5:05 dmr
2004-08-20  5:35 ` George Michaelson

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=53811f0a56be6321b1fe11d35ee21d21@collyer.net \
    --to=geoff@collyer.net \
    --cc=9fans@cse.psu.edu \
    /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).