From: Patrick McHardy <kaber@trash.net>
To: Julien Vehent <julien@linuxwall.info>
Cc: netdev@vger.kernel.org
Subject: Re: can SFQ and perturb break paquet ordering ?
Date: Wed, 10 Mar 2010 13:30:10 +0100 [thread overview]
Message-ID: <4B9790D2.7030005@trash.net> (raw)
In-Reply-To: <ca4f1a12b3ba9c81f3276c091063613f@localhost>
Julien Vehent wrote:
> Hi netdev folks,
>
> I was digging into the sch_sfq code and I was wondering the following (I
> assume it's nothing new, I'm just trying to get it right):
>
> Let's consider one UDP connection that has two packets. Packet#1 goes to
> bucket#1, then perturb modifies the hashing algorithms and thus Packet#2
> goes to bucket#800.
>
> If the round robin was positionned after bucket#1 but before bucket#800
> when perturb occured, then Packet#2 will be sent before Packet#1. And since
> UDP can't reordered, it will be processed before on the received end.
>
> Am I getting this right or is there something in the code that I missed ?
That's correct.
prev parent reply other threads:[~2010-03-10 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 12:22 can SFQ and perturb break paquet ordering ? Julien Vehent
2010-03-10 12:30 ` Patrick McHardy [this message]
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=4B9790D2.7030005@trash.net \
--to=kaber@trash.net \
--cc=julien@linuxwall.info \
--cc=netdev@vger.kernel.org \
/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).