From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH 2.6] (1/4) netem - update API for new features
Date: Wed, 25 Aug 2004 16:25:13 -0700 [thread overview]
Message-ID: <20040825162513.52bdeadf.davem@redhat.com> (raw)
In-Reply-To: <20040825105339.30210e84@dell_ss3.pdx.osdl.net>
On Wed, 25 Aug 2004 10:53:39 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> Extend netem options to support new features.
This breaks all existing tc binaries. We have to stop
doing this.
Yes, you can extend the structure, but when you do that you
have to teach functions like netem_change() how to cope
with the old structure layout.
next prev parent reply other threads:[~2004-08-25 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 17:53 [PATCH 2.6] (1/4) netem - update API for new features Stephen Hemminger
2004-08-25 17:57 ` [PATCH 2.6] (2/4) netem - comment update Stephen Hemminger
2004-08-25 17:59 ` [PATCH 2.6] (3/4) netem - support packet duplication Stephen Hemminger
2004-08-25 18:01 ` [PATCH 2.6] (4/4) netem - change parameters shouldn't destroy child qdisc Stephen Hemminger
2004-08-25 23:15 ` [PATCH 2.6] netem - add correlated random number support Stephen Hemminger
2004-08-25 23:52 ` David S. Miller
2004-08-25 18:08 ` [PATCH 2.6] netem - configurable distributions Stephen Hemminger
2004-08-25 20:50 ` [PATCH 2.4] netem -- update to match new 2.6 version Stephen Hemminger
2004-08-25 23:25 ` David S. Miller [this message]
2004-08-26 12:08 ` [PATCH 2.6] (1/4) netem - update API for new features jamal
2004-08-26 16:16 ` Stephen Hemminger
2004-08-26 18:13 ` jamal
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=20040825162513.52bdeadf.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).