netdev
[Top] [All Lists]

Re: RFC/PATCH capture qdisc requeue event in stats

To: hadi@xxxxxxxxxx
Subject: Re: RFC/PATCH capture qdisc requeue event in stats
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Mon, 30 Aug 2004 21:29:10 -0700
Cc: netdev@xxxxxxxxxxx, shemminger@xxxxxxxx
In-reply-to: <1093919823.1043.80.camel@xxxxxxxxxxxxxxxx>
References: <1093799632.1073.410.camel@xxxxxxxxxxxxxxxx> <20040830144033.2265a6e6.davem@xxxxxxxxxx> <1093904088.1043.12.camel@xxxxxxxxxxxxxxxx> <20040830154430.769d1d59.davem@xxxxxxxxxx> <1093906592.1037.32.camel@xxxxxxxxxxxxxxxx> <20040830160052.548c4846.davem@xxxxxxxxxx> <1093916592.1037.51.camel@xxxxxxxxxxxxxxxx> <20040830191716.0d002f91.davem@xxxxxxxxxx> <1093919823.1043.80.camel@xxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On 30 Aug 2004 22:37:03 -0400
jamal <hadi@xxxxxxxxxx> 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.

<Prev in Thread] Current Thread [Next in Thread>