[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.WNT.2.00.1010281405001.11080@jbrandeb-desk1.amr.corp.intel.com>
Date: Thu, 28 Oct 2010 14:10:30 -0700 (Pacific Daylight Time)
From: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To: Ben Hutchings <bhutchings@...arflare.com>
cc: "jgarzik@...hat.com" <jgarzik@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Wyborny, Carolyn" <carolyn.wyborny@...el.com>
Subject: Re: ethtool: missing implementation of n_priv_flags
On Thu, 28 Oct 2010, Ben Hutchings wrote:
> Brandeburg, Jesse wrote:
> > Was just looking at implementing the driver private flags to add a new feature to
> > a driver.
> >
> > It appears that nothing in the core ethtool.c ever accesses or prints n_priv_flags,
> > even if a driver assigns it (which none in the kernel currently do)
> [...]
>
> You mean net/core/ethtool.c? Or the ethtool utility?
The ethtool utility (the app that would print the 1-1 match between bits
and strings)
> If you set it in your get_drvinfo() operation then it will be copied out.
> As for the ethtool utility, I've implemented some generic flag parsing and
> printing functionality so it shouldn't be too hard to use that for private
> flags.
Right, I see the code where it gets copied into drvinfo in the kernel but
nothing ever prints it on the userspace side.
We'll take a shot at an implementation in the ethtool proper and post it
(hopefully soon). I imagine it will just be printed when one runs the
command
# ethtool ethX
and the set side will probably be implemented as part of -s
# ethtool -s ethX pflag [0-0xFFFFFFFF]
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists