All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Samsel <csamsel@gmxpro.de>
To: Stephen Hemminger <shemminger@vyatta.com>, netdev@vger.kernel.org
Cc: Stephen Hemminger <shemminger@osdl.org>
Subject: Re: [PATCH 1/2] improve netem reorder flexibility
Date: Fri, 18 Dec 2009 18:56:59 +0100	[thread overview]
Message-ID: <200912181856.59901.csamsel@gmxpro.de> (raw)
In-Reply-To: <20091218093240.64ca7d88@nehalam>

Am Freitag, 18. Dezember 2009 18:32:40 schrieb Stephen Hemminger:
> On Fri, 18 Dec 2009 14:18:37 +0100
> 
> Christian Samsel <christian.samsel@rwth-aachen.de> wrote:
> > This patch adds a new feature to netem: The newly introduced parameter
> > reorderdelay TIME is the time a reordered packet is delayed. It can be
> > used in a combination with delay TIME to enable netem to produce late
> > packets, which is not possible in the standard netem / iproute2. In the
> > standard version reordered packets are always sent immediately and
> > therefore are always early packets.
> 
> I like the idea but is it binary compatible with older kernels/ older
>  iproute2 utilities?
> 
Thats a good point. I will test it. So far i think it should work.

  reply	other threads:[~2009-12-18 17:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 13:18 [PATCH 1/2] improve netem reorder flexibility Christian Samsel
2009-12-18 13:18 ` [PATCH 2/2] " Christian Samsel
2009-12-18 17:32 ` [PATCH 1/2] " Stephen Hemminger
2009-12-18 17:56   ` Christian Samsel [this message]
2009-12-18 18:01   ` Christian Samsel
2009-12-19  3:59     ` David Miller
2009-12-19 10:38       ` Christian Samsel
2009-12-21 17:54       ` Stephen Hemminger
2010-01-16  9:46         ` David Miller
2010-01-17 12:11           ` Christian Samsel
2010-01-18  2:56             ` David Miller
2010-01-18  5:44               ` Stephen Hemminger

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=200912181856.59901.csamsel@gmxpro.de \
    --to=csamsel@gmxpro.de \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --cc=shemminger@vyatta.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 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.