From: Jeff Garzik <jeff@garzik.org>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] e1000e: export some settings using ethtool private flags
Date: Thu, 25 Mar 2010 13:30:24 -0400 [thread overview]
Message-ID: <4BAB9DB0.7020203@garzik.org> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365FE4B3E5A7@rrsmsx501.amr.corp.intel.com>
On 03/25/2010 01:16 PM, Tantilov, Emil S wrote:
> Jeff Garzik wrote:
>> The ethtool private flags interface exists to get/set driver-specific
>> settings at runtime, in a flexible manner.
>>
>> Use this facility to export a couple e1000e features, that were
>> previously only set at module initialization time.
>>
>> Signed-off-by: Jeff Garzik<jgarzik@redhat.com>
>> ---
>> drivers/net/e1000e/ethtool.c | 27 +++++++++++++++++++++++++++
>> 1 file changed, 27 insertions(+)
>
> Jeff,
>
> What is the use case for the ethtool private flags?
It is stated in the changelog above :) It enables feature setting at
setting, on an easy, per-network-interface basis, that were previously
only settable at module initialization (ie. load) time.
> At least I don't see an option in ethtool that would make use of them.
This is added in a separate patch, since the above patch is the first to
make use of the private-flags ethtool mechanism.
Jeff
next prev parent reply other threads:[~2010-03-25 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 8:23 [PATCH] e1000e: export some settings using ethtool private flags Jeff Garzik
2010-03-25 17:16 ` Tantilov, Emil S
2010-03-25 17:30 ` Jeff Garzik [this message]
2010-03-25 17:33 ` Tantilov, Emil S
2010-03-25 17:52 ` Laurent Chavey
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=4BAB9DB0.7020203@garzik.org \
--to=jeff@garzik.org \
--cc=emil.s.tantilov@intel.com \
--cc=netdev@vger.kernel.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