Netdev List
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: [Netem] [PATCH] (1/3) netem - reinsert for duplication
Date: Thu, 19 May 2005 16:32:35 -0700	[thread overview]
Message-ID: <20050519163235.2f5db193@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <20050519151250.17ab5c81@dxpl.pdx.osdl.net>

On Thu, 19 May 2005 15:12:50 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:

> Handle duplication of packets in netem by re-inserting at top of qdisc tree.
> This avoid problems with qlen accounting with nested qdisc. This recursion
> requires no additional locking but will potentially increase stack depth.
> 
> Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
> 

Hold off on applying these patches until next week, I am seeing some timing
anomalies when using this for TCP testing, and not sure if these patches are related.

  reply	other threads:[~2005-05-19 23:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 22:12 [PATCH] (1/3) netem - reinsert for duplication Stephen Hemminger
2005-05-19 23:32 ` Stephen Hemminger [this message]
2005-05-19 23:37   ` [Netem] " David S. Miller

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=20050519163235.2f5db193@dxpl.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=davem@davemloft.net \
    --cc=netdev@oss.sgi.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