From: Stephen Hemminger <stephen@networkplumber.org>
To: francois.michel@uclouvain.be
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2 iproute2-next 0/2] tc: support the netem seed parameter for loss and corruption events
Date: Wed, 23 Aug 2023 06:16:52 -0700 [thread overview]
Message-ID: <20230823061652.41c238dc@hermes.local> (raw)
In-Reply-To: <20230823100128.54451-1-francois.michel@uclouvain.be>
On Wed, 23 Aug 2023 12:01:08 +0200
francois.michel@uclouvain.be wrote:
> From: François Michel <francois.michel@uclouvain.be>
>
> Linux now features a seed parameter to guide and reproduce
> the loss and corruption events. This patch integrates these
> results in the tc CLI.
>
> For instance, setting the seed 42424242 on the loopback
> with a loss rate of 10% will systematically drop the 5th,
> 12th and 24th packet when sending 25 packets.
>
> v1 -> v2: Address comments and output the seed value
> *after* slot information in netem_print_opt().
Daid will pickup the pkt_sched.h changes as part of regular header update
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2023-08-23 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 10:01 [PATCH v2 iproute2-next 0/2] tc: support the netem seed parameter for loss and corruption events francois.michel
2023-08-23 10:01 ` [PATCH v2 iproute2-next 1/2] " francois.michel
2023-08-29 10:07 ` Petr Machata
2023-08-30 12:30 ` François Michel
2023-08-30 13:22 ` Petr Machata
2023-08-30 15:01 ` David Ahern
2023-08-23 10:01 ` [PATCH v2 iproute2-next 2/2] man: tc-netem: add section for specifying the netem seed francois.michel
2023-08-23 13:16 ` Stephen Hemminger [this message]
2023-08-29 3:00 ` [PATCH v2 iproute2-next 0/2] tc: support the netem seed parameter for loss and corruption events patchwork-bot+netdevbpf
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=20230823061652.41c238dc@hermes.local \
--to=stephen@networkplumber.org \
--cc=francois.michel@uclouvain.be \
--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).