From: Matthew Wilcox <willy@debian.org>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: Matthew Wilcox <willy@debian.org>,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [PATCH] ethtool_ops
Date: Mon, 30 Jun 2003 17:31:01 +0100 [thread overview]
Message-ID: <20030630163101.GI31618@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E010107D8CD@orsmsx402.jf.intel.com>
(sorry for the delayed reply; PCI domain work got a lot more important
for a while)
On Fri, Jun 06, 2003 at 01:17:46PM -0700, Feldman, Scott wrote:
> * On get_gregs, for example, would it make sense to ->get_drvinfo
> so you'll know regdump_len and therefore can kmalloc an ethtool_regs
> with enough space to pass to ->get_regs? Keep the kmalloc and
> kfree together. Same for self_test, get_strings, and get_stats.
> For get_strings, size = max{n_stats, testinfo_len)*sizeof(u64).
That would be one possibility, but get_drvinfo is quite heavyweight.
I think I'd prefer to not do that unless there's a strong feeling about
thing.
> * If the above is done, can we have one function type for the
> ethtool_ops
> functions? int f(struct netdev *, struct ethtool_cmd *). The
> drawback is the driver needs to cast to the specific ethtool_* struct.
Definitely not -- the point is adding type safety.
> * Can we get an HAVE_ETHTOOL_OPS defined in netdevice.h to support
> backward compat?
I'm hoping to avoid that by getting compatibility code merged into 2.4.22.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-06-30 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 20:17 Feldman, Scott
2003-06-07 19:09 ` Jeff Garzik
2003-06-30 16:31 ` Matthew Wilcox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-30 18:46 Feldman, Scott
2003-06-06 14:29 Matthew Wilcox
2003-06-06 14:31 ` David S. Miller
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=20030630163101.GI31618@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=scott.feldman@intel.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
all inboxes | Powered by JetHome®