mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /dev/random probs in 2.4test(12-pre3)
Date: Sun, 03 Dec 2000 23:20:36 +1100	[thread overview]
Message-ID: <3A2A3A94.167C4D20@uow.edu.au> (raw)
In-Reply-To: <200012022318.SAA17498@tsx-prime.MIT.EDU> <Pine.GSO.4.21.0012021830090.28923-100000@weyl.math.psu.edu>

Alexander Viro wrote:
> 
> Erm... Not that ignoring the return values was a bright idea, but the
> lack of reliable ordered datagram protocol in IP family is not a good
> thing. It can be implemented over TCP, but it's a big overkill. IL is a
> nice thing to have...

Pet peeve?  There are about five "reliable UDPs" floating
around.  Take a look at

	http://www.faqs.org/rfcs/rfc2960.html

SCTP is mainly designed as a way of transporting telephony signalling
information across IP.  But it is now a quite general purpose protocol.

Culturally, this is "Telephony industry comes to IP.  Telephony
industry is appalled.  IP industry gets a clue".

SCTP provides the reliable delivery of messages to which you refer.
It's slightly more efficient than TCP for a given set of network
characteristics - there's no statement about implementation
efficiency here. No head-of-line blocking issues.

One very interesting part of SCTP is that transport endpoints are
explicitly set up between *hosts*, not between IP addresses.  The
protocol is designed around multihomed hosts.

I don't know if anyone has looked into mapping SCTP capabilities onto
the BSD socket API.  It may be hard.

The reference implementation is for userland Linux.  It's at
ftp://standards.nortelnetworks.com/sigtran/

A good kernel-mode implementation of SCTP for Linux would be
a very big project.  But also a very big contribution.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-03 12:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-01 17:33 folkert
2000-12-02 11:09 ` Matthew Kirkwood
2000-12-02 18:58   ` Igmar Palsenberg
2000-12-02 18:03     ` Jeff Garzik
2000-12-02 21:32       ` Igmar Palsenberg
2000-12-02 20:42         ` David Ford
2000-12-02 22:00           ` Albert D. Cahalan
2000-12-02 23:18             ` Theodore Y. Ts'o
2000-12-02 23:34               ` Alexander Viro
2000-12-03  3:01                 ` Theodore Y. Ts'o
2000-12-03 12:20                 ` Andrew Morton [this message]
2000-12-03 16:32               ` Igmar Palsenberg
2000-12-03  7:20             ` H. Peter Anvin
2000-12-03  7:41               ` Albert D. Cahalan
2000-12-03 16:25           ` Igmar Palsenberg
2000-12-03 18:52             ` Jeff Garzik
2000-12-03 21:18               ` Igmar Palsenberg
2000-12-03 20:15                 ` David Ford
2000-12-03  7:17         ` H. Peter Anvin
2000-12-19 19:24           ` Kai Henningsen
2000-12-02 21:35       ` Igmar Palsenberg
2000-12-02 20:44         ` David Ford
2000-12-03 16:27           ` Igmar Palsenberg
2000-12-03  7:19         ` H. Peter Anvin
2000-12-03  7:16     ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2000-12-01 17:26 Matthew Kirkwood
2000-12-01 18:18 ` H. Peter Anvin
2000-12-02 12:01   ` Matthew Kirkwood

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=3A2A3A94.167C4D20@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.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

all inboxes | Powered by JetHome®