From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: netdev_ops?
Date: Tue, 22 Jul 2003 23:36:25 -0700 [thread overview]
Message-ID: <3F1E2CE9.2080404@candelatech.com> (raw)
In-Reply-To: <20030722232719.216d7823.davem@redhat.com>
David S. Miller wrote:
> You gain nothing from this patch, just put it into your drivers.
I am not writing drivers, I'm trying to write code that works with
everything that looks remotely like an ethernet device. Thus,
I can make this one change and work with ALL drivers, and not have
to corrupt every friggin driver under the sun.
And yes, I realize this patch is not adding a new ioctl..that is the
whole point.
>
> Your patch is even more useless than I thought it was going to
> be. :-)
I really hope you mis-understood it :)
Note it allows me to get a binary representation of the net_device_stats
w/out having to parse /proc/net/dev or figure out the vast complexity
of libnetlink.
I have plenty of other things that are currently new ioctls that could
be handled the same, and thus I could continue to avoid issues with
other platforms.
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2003-07-23 6:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 5:06 netdev_ops? Ben Greear
2003-07-23 5:07 ` netdev_ops? David S. Miller
2003-07-23 5:30 ` netdev_ops? Ben Greear
2003-07-23 6:02 ` netdev_ops? David S. Miller
2003-07-23 6:24 ` netdev_ops? Ben Greear
2003-07-23 6:27 ` netdev_ops? David S. Miller
2003-07-23 6:36 ` Ben Greear [this message]
2003-07-23 7:01 ` netdev_ops? David S. Miller
2003-07-23 7:28 ` netdev_ops? Ben Greear
2003-07-23 7:34 ` netdev_ops? David S. Miller
2003-07-23 8:08 ` netdev_ops? Ben Greear
2003-07-23 8:15 ` netdev_ops? David S. Miller
2003-07-23 16:59 ` netdev_ops? Jeff Garzik
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=3F1E2CE9.2080404@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
/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).