From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Andrew McGregor <andrew@indranet.co.nz>,
Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>,
"David S. Miller" <davem@redhat.com>,
dlstevens@us.ibm.com, matti.aarnio@zmailer.org,
alan@lxorguk.ukuu.org.uk, stefano.andreani.ap@h3g.it,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: R: Kernel bug handling TCP_RTO_MAX?
Date: Sat, 14 Dec 2002 00:58:19 +0200 [thread overview]
Message-ID: <20021213225819.GO32122@mea-ext.zmailer.org> (raw)
In-Reply-To: <3DFA21C5.867C6320@us.ibm.com>
On Fri, Dec 13, 2002 at 10:07:01AM -0800, Nivedita Singhvi wrote:
> Andrew McGregor wrote:
> > In a closed network, why not have SOCK_STREAM map to something faster than
> > TCP anyway? That is, if I connect(address matching localnet), SOCK_STREAM
> > maps to (eg) SCTP. That would be a far more dramatic performance hack!
> >
> > Andrew
>
> Not that simple. SCTP (if that is what Matti was referring to) is
> a SOCK_STREAM socket, with a protocol of IPPROTO_SCTP. I'm just
> getting done implementing a testsuite against the SCTP API.
Most likely that is what I did mean.
Things in IETF do on occasion change names, or I don't always
remember all characters in (E)TLA-acronyms I use rarely...
...
> But dont expect SCTP to be the surreptitious underlying layer
> carrying TCP traffic, if thats an expectation that anyone has :)
At least I didn't expect that, don't know of others.
It all depends on application coders, if users will be able
to use arbitrary network protocols -- say any SOCK_STREAM
protocol supported now, and in future by system kernel.
Ever heard of "TLI" ?
> Solving this problem without application involvement is a
> more limited scenario..
Yes, but sufficiently important to occasionally.
Doing things like this mapping might make limited sense
via routing table lookups.
> thanks,
> Nivedita
/Matti Aarnio
next prev parent reply other threads:[~2002-12-13 22:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 6:55 David Stevens
2002-12-13 6:59 ` David S. Miller
2002-12-13 11:46 ` Bogdan Costescu
2002-12-13 11:48 ` Andrew McGregor
2002-12-13 12:33 ` Bogdan Costescu
2002-12-13 13:07 ` Andrew McGregor
2002-12-13 18:07 ` Nivedita Singhvi
2002-12-13 22:25 ` Andrew McGregor
2002-12-13 22:58 ` Matti Aarnio [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 20:37 Nivedita Singhvi
2002-12-12 20:18 Andreani Stefano
2002-12-12 20:32 ` David S. Miller
2002-12-12 21:16 ` Alan Cox
2002-12-13 2:26 ` Nivedita Singhvi
2002-12-13 3:39 ` Matti Aarnio
2002-12-13 4:45 ` Nivedita Singhvi
2002-12-13 6:26 ` Nivedita Singhvi
2002-12-13 11:40 ` Andrew McGregor
2002-12-13 5:23 ` David S. Miller
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=20021213225819.GO32122@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrew@indranet.co.nz \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=davem@redhat.com \
--cc=dlstevens@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=niv@us.ibm.com \
--cc=stefano.andreani.ap@h3g.it \
/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®