netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kc <nirvana.code@gmail.com>
To: "Majumder, Rajib" <rajib.majumder@credit-suisse.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: UDP Out 0f Sequence
Date: Wed, 20 Sep 2006 19:13:15 +0530	[thread overview]
Message-ID: <e92e3a770609200643m55603f50u10a597a6dc5001aa@mail.gmail.com> (raw)
In-Reply-To: <F444CAE5E62A714C9F45AA292785BED30EB97591@esng11p33001.sg.csfb.com>

network transit. different datagrams might go through different
routes, hence the out-of-sequence arrival.

On 9/20/06, Majumder, Rajib <rajib.majumder@credit-suisse.com> wrote:
> Hi,
>
> If I write UDP datagrams 1,2 and 3 to network and if the receiver receives in order 2,1, and 3, where can the sequence get changed? Is it at the source stack, network transit or destination stack?
>
> Any reply is highly appreciated.
>
> Thanks
>
> Rajib
>
> ==============================================================================
> Please access the attached hyperlink for an important electronic communications disclaimer:
>
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> ==============================================================================
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2006-09-20 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20  7:13 UDP Out 0f Sequence Majumder, Rajib
2006-09-20 13:43 ` kc [this message]
2006-09-20 16:47 ` Rick Jones
  -- 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-21  3:55 Majumder, Rajib
2006-09-21 16:42 ` Rick Jones
2007-09-28 17:22   ` Randy Macleod

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=e92e3a770609200643m55603f50u10a597a6dc5001aa@mail.gmail.com \
    --to=nirvana.code@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rajib.majumder@credit-suisse.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).