From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Julio Kriger" <juliokriger@gmail.com>
Cc: netdev@vger.kernel.org, netdev@oss.sgi.com,
netem@linux-foundation.org, netem@lists.linux-foundation.org
Subject: Re: [Netem] Fixed delay patch for netem
Date: Mon, 25 Feb 2008 16:54:28 -0800 [thread overview]
Message-ID: <20080225165428.24ee90fe@extreme> (raw)
In-Reply-To: <682bc30a0802240611r5670fc9etba66cf86a9a78113@mail.gmail.com>
On Sun, 24 Feb 2008 12:11:16 -0200
"Julio Kriger" <juliokriger@gmail.com> wrote:
> Hi!
> I have created this patch to add a fixed delay on packet filtered by
> netem. Soon I will send the patch to iproute2.
> This patch comes from a need I have to delay all packets 50ms, beside
> the actual delay setting, like 30ms +- 15 ms.
Why is 50ms + 30m +/- 15ms any different than 80ms +/- 15ms
> This strike, IMMHO, a
> missing point on gap reordering. If I set "gap 5 delay 10ms" every 5th
> (10th, 15th, ...) packet to go to be sent immediately and every other
> packet to be delayed by 10ms. This is ok, but I also need a "fixed"
> delay of 50ms to be applied to all packets. Since netem can't be
> nested with himself (so I can do a fixed delay), I needed this new
> feature on netem.
The gap stuff is an awkward interface that should/could have been
done better.
> This patch was create with linux kernel version 2.6.24.2.
> I hope you like it, and it would be great if it goes shiped with the
> next version of the kernel :-))
> Regards,
> Julio Kriger
Maybe, but it is getting confusing with all the growth of parameters.
Probably time for a rethink.
next prev parent reply other threads:[~2008-02-26 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 14:11 Fixed delay patch for netem Julio Kriger
2008-02-26 0:54 ` Stephen Hemminger [this message]
2008-02-26 11:45 ` [Netem] " Julio Kriger
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=20080225165428.24ee90fe@extreme \
--to=shemminger@linux-foundation.org \
--cc=juliokriger@gmail.com \
--cc=netdev@oss.sgi.com \
--cc=netdev@vger.kernel.org \
--cc=netem@linux-foundation.org \
--cc=netem@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.