From: "David S. Miller" <davem@davemloft.net>
To: hadi@cyberus.ca
Cc: netdev@oss.sgi.com, shemminger@osdl.org
Subject: Re: RFC/PATCH capture qdisc requeue event in stats
Date: Mon, 30 Aug 2004 21:29:10 -0700 [thread overview]
Message-ID: <20040830212910.78047bcd.davem@davemloft.net> (raw)
In-Reply-To: <1093919823.1043.80.camel@jzny.localdomain>
On 30 Aug 2004 22:37:03 -0400
jamal <hadi@cyberus.ca> wrote:
> thmart. Lets go with this then. Steve, do you wanna take it from here
> with the iproute2 patch i sent or you want me to generate a new one? Now
> how do we tell all other people who have written netlink apps
> to beware?
Yeah, how are you going to "tell those other people"? And how
are you going to get every user to know to upgrade all of those
apps when they try to use a kernel with your patch applied?
Look, let's get real about this topic. We can't be breaking shit
like this all the time. We're nearly letting it happen a lot
lately.
These data structures are user visible APIs, they are just like
system call data structures, and if we cannot modify
them without potentially breaking some existing application we
cannot make that change.
So please find another way to add make this statistic visible to
userspace Jamal. Thanks a lot.
next prev parent reply other threads:[~2004-08-31 4:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 17:13 RFC/PATCH capture qdisc requeue event in stats jamal
2004-08-30 21:40 ` David S. Miller
2004-08-30 22:14 ` jamal
2004-08-30 22:44 ` David S. Miller
2004-08-30 22:56 ` jamal
2004-08-30 23:00 ` David S. Miller
2004-08-31 1:43 ` jamal
2004-08-31 2:17 ` David S. Miller
2004-08-31 2:37 ` jamal
2004-08-31 4:29 ` David S. Miller [this message]
2004-08-31 18:09 ` jamal
2004-09-29 0:36 ` Thomas Graf
2004-09-29 2:54 ` jamal
2004-09-29 12:48 ` Thomas Graf
2004-09-29 14:08 ` jamal
2004-08-30 23:05 ` Stephen Hemminger
2004-09-28 23:10 ` Stephen Hemminger
2004-09-28 23:18 ` David S. Miller
2004-09-29 0:01 ` Stephen Hemminger
2004-09-29 0:03 ` David S. Miller
2004-09-29 2:31 ` 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=20040830212910.78047bcd.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--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).