From: Claudiu Manoil <claudiu.manoil@freescale.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <paul.gortmaker@windriver.com>
Subject: Re: [PATCH net-next] gianfar: Change default HW Tx queue scheduling mode
Date: Mon, 24 Sep 2012 13:46:43 +0300 [thread overview]
Message-ID: <50603A13.3030709@freescale.com> (raw)
In-Reply-To: <20120921.133528.2219558580262606729.davem@davemloft.net>
On 09/21/2012 08:35 PM, David Miller wrote:
> From: Claudiu Manoil <claudiu.manoil@freescale.com>
> Date: Thu, 20 Sep 2012 18:57:54 +0300
>
>> The TXSCHED setting may be changed at runtime, via sysfs, for devices
>> using multiple H/W Tx queues. For single queue devices this config
>> option is disabled, as the TXSCHED setting is superfluous in those cases.
>
> Please, no special driver specific sysfs knobs.
>
> Extend ethtool as necessary for your needs, so that any driver can
> provide this kind of configurability in a consistent way for users..
>
Ok.
Resent the patch addressing the watchdog timeout issue, without the
runtime configuration part.
(see http://patchwork.ozlabs.org/patch/186315/).
This config option seems to be better off in a separate patch,
especially if it would imply changes to ethtool.
What would you think of such an ethtool extension? Beside allowing the
user to choose b/w letting the H/W to service its Tx queues equally or
according to a built-in priority scheme, it could also provide api to
configure scheduling weights per Tx queue for a weighted round-robin
queue selection scheme, or, to configure only a single weight for all
the queues (for a balanced scheme). (Are there currently other drivers/
devices that would use such an option?)
Thanks,
Claudiu
prev parent reply other threads:[~2012-09-24 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 15:57 [PATCH net-next] gianfar: Change default HW Tx queue scheduling mode Claudiu Manoil
2012-09-21 17:35 ` David Miller
2012-09-24 10:46 ` Claudiu Manoil [this message]
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=50603A13.3030709@freescale.com \
--to=claudiu.manoil@freescale.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.