From: David Miller <davem@davemloft.net>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC 1/4] net: support per queue tx_usecs in sysfs
Date: Tue, 01 Dec 2015 21:27:00 -0500 (EST) [thread overview]
Message-ID: <20151201.212700.1291998408162014445.davem@davemloft.net> (raw)
In-Reply-To: <20151201154454.000041a3@unknown>
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
Date: Tue, 1 Dec 2015 15:44:54 -0800
> While I agree that ethtool provides a similar functionality, ethtool
> was designed (particularly the ethtool -C/c commands) around one queue
> NICs. We can't change the output or functionality of the user
> interface without breaking a bunch of user's scripts and stuff.
See my suggestion, we can encapsulate existing ethtool commands inside
of a new command that specifies operations that are to be applied to
specific queues.
Do not use sysfs for this.
next prev parent reply other threads:[~2015-12-02 2:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 8:01 [Intel-wired-lan] [RFC 1/4] net: support per queue tx_usecs in sysfs kan.liang
2015-12-01 8:01 ` [Intel-wired-lan] [RFC 2/4] i40e: handle per queue tx_usecs setting kan.liang
2015-12-01 8:01 ` [Intel-wired-lan] [RFC 3/4] net: support per queue rx_usecs in sysfs kan.liang
2015-12-01 8:01 ` [Intel-wired-lan] [RFC 4/4] i40e: handle per queue rx_usecs setting kan.liang
2015-12-01 19:47 ` Stephen Hemminger
2015-12-01 22:13 ` [Intel-wired-lan] [RFC 1/4] net: support per queue tx_usecs in sysfs Florian Fainelli
2015-12-01 23:44 ` Jesse Brandeburg
2015-12-02 1:57 ` Alexander Duyck
2015-12-02 2:27 ` David Miller [this message]
2015-12-02 2:23 ` David 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=20151201.212700.1291998408162014445.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=intel-wired-lan@osuosl.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