From: "Randy Macleod" <macleodr@nortel.com>
To: "Majumder, Rajib" <rajib.majumder@credit-suisse.com>
Cc: Rick Jones <rick.jones2@hp.com>,
"'David Miller'" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: UDP Out 0f Sequence
Date: Fri, 28 Sep 2007 13:22:28 -0400 [thread overview]
Message-ID: <46FD3854.8010702@nortel.com> (raw)
In-Reply-To: <4512C10A.4070303@hp.com>
Rick Jones wrote:
> Majumder, Rajib wrote:
>> Let's say we have 2 uniprocessor hosts connected back to back. Is
>> there any possibility of an out-of-order scenario on recv?
>
> Your application should be written on the assumption that it is
> possible, regardless of the specifics of the hosts involved, however
> unlikely they may be to reorder traffic.
>
> > Is this same for all kernel (linux/solaris)?
>
> Your application should be written on the assumtion that it is possible,
> regardless of the specifics of the OSes involved, however unlikely they
> may be to reorder traffic.
Or you should use a different protocol stack that guarantees order.
Have you considered TCP, DCCP or even TIPC?
The solution depends on your application requirements and your
projects tolerance for risk.
// Randy
next prev parent reply other threads:[~2007-09-28 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 3:55 UDP Out 0f Sequence Majumder, Rajib
2006-09-21 16:42 ` Rick Jones
2007-09-28 17:22 ` Randy Macleod [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-21 2:50 Majumder, Rajib
2006-09-21 3:51 ` David Miller
2006-09-21 3:59 ` Ian McDonald
2006-09-20 7:13 Majumder, Rajib
2006-09-20 13:43 ` kc
2006-09-20 16:47 ` Rick Jones
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=46FD3854.8010702@nortel.com \
--to=macleodr@nortel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rajib.majumder@credit-suisse.com \
--cc=rick.jones2@hp.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;
as well as URLs for NNTP newsgroup(s).