netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com, shemminger@osdl.org
Subject: Re: RFC/PATCH capture qdisc requeue event in stats
Date: 31 Aug 2004 14:09:13 -0400	[thread overview]
Message-ID: <1093975753.1052.14.camel@jzny.localdomain> (raw)
In-Reply-To: <20040830212910.78047bcd.davem@davemloft.net>

On Tue, 2004-08-31 at 00:29, David S. Miller wrote:
> 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?


Again, thats not an issue. new kernel. old app should work
Challenge is old kernel, new app.

> 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.

Agreed.

> 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.

Well, Franks A Lot(TM) Dave ;->
Let me rethink - I will be back.

cheers,
jamal

  reply	other threads:[~2004-08-31 18:09 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
2004-08-31 18:09                   ` jamal [this message]
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=1093975753.1052.14.camel@jzny.localdomain \
    --to=hadi@cyberus.ca \
    --cc=davem@davemloft.net \
    --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).