From: Teco Boot <teco@inf-net.nl>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Ferry Huberts <mailings@hupie.com>,
Netem <netem@lists.linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"core-users@pf.itd.nrl.navy.mil" <core-users@pf.itd.nrl.navy.mil>
Subject: Re: netem: the reorder discussion
Date: Fri, 23 Aug 2013 18:18:44 +0200 [thread overview]
Message-ID: <DF05DAC3-CED7-4615-AC02-F097EEC27752@inf-net.nl> (raw)
In-Reply-To: <1377273838.8828.11.camel@edumazet-glaptop>
Op 23 aug. 2013 om 18:03 heeft Eric Dumazet <eric.dumazet@gmail.com> het volgende geschreven:
> On Fri, 2013-08-23 at 17:53 +0200, Teco Boot wrote:
>
>> Questions that pops out of of my head: What is more important,
>> understandable configuration or keep existing behavior for unmodified
>> configuration? Do we want to reorder, even with configured rate?
>>
>> My preference: make in understandable, document well and make all
>> sensible options available.
>
> The day 'rate' support was added, documentation became obsolete.
>
> Its actually hard to have both rate and delay + jitters + reorders or
> not.
>
> If you can fix this properly, patches are welcome, but I suspect you
> wanted to reintroduce the thing that made netem unusable for us.
No, for sure I do not want to make it unusable for you. Or anybody. The opposite is true.
I don't like the "look in souce" documentation. Or parameters with hard to understand side effects.
prev parent reply other threads:[~2013-08-23 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 14:16 netem: the reorder discussion Teco Boot
2013-08-23 15:12 ` Eric Dumazet
2013-08-23 15:44 ` Stephen Hemminger
2013-08-23 15:53 ` Teco Boot
2013-08-23 16:03 ` Eric Dumazet
2013-08-23 16:18 ` Teco Boot [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=DF05DAC3-CED7-4615-AC02-F097EEC27752@inf-net.nl \
--to=teco@inf-net.nl \
--cc=core-users@pf.itd.nrl.navy.mil \
--cc=eric.dumazet@gmail.com \
--cc=mailings@hupie.com \
--cc=netdev@vger.kernel.org \
--cc=netem@lists.linux-foundation.org \
--cc=stephen@networkplumber.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).