[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <543141AC.3060006@cogentembedded.com>
Date: Sun, 05 Oct 2014 17:03:40 +0400
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: Amir Vadai <amirv@...lanox.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>
CC: netdev@...r.kernel.org, Yevgeny Petrilin <yevgenyp@...lanox.com>,
Or Gerlitz <ogerlitz@...lanox.com>,
Ido Shamay <idos@...lanox.com>
Subject: Re: [PATCH net-next 14/14] net/mlx4_en: Use the new tx_copybreak
to set inline threshold
Hello.
On 10/5/2014 1:35 PM, Amir Vadai wrote:
> From: Eric Dumazet <edumazet@...gle.com>
> Instead of setting inline threshold using module parameter only on
> driver load, use set_tunable() to set it dynamically.
> No need to store the threshold per ring, using instead the netdev global
> priv->prof->inline_thold
> Initial value still is set using the module parameter, therefore
> backward compatability is kept.
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
> Signed-off-by: Amir Vadai <amirv@...lanox.com>
> ---
> drivers/net/ethernet/mellanox/mlx4/en_ethtool.c | 44 +++++++++++++++++++++++++
> drivers/net/ethernet/mellanox/mlx4/en_tx.c | 1 -
> drivers/net/ethernet/mellanox/mlx4/mlx4_en.h | 1 -
> 3 files changed, 44 insertions(+), 2 deletions(-)
> diff --git a/drivers/net/ethernet/mellanox/mlx4/en_ethtool.c b/drivers/net/ethernet/mellanox/mlx4/en_ethtool.c
> index 42c9f8b..ae83da9 100644
> --- a/drivers/net/ethernet/mellanox/mlx4/en_ethtool.c
> +++ b/drivers/net/ethernet/mellanox/mlx4/en_ethtool.c
[...]
> @@ -1297,6 +1339,8 @@ const struct ethtool_ops mlx4_en_ethtool_ops = {
> .get_ts_info = mlx4_en_get_ts_info,
> .set_priv_flags = mlx4_en_set_priv_flags,
> .get_priv_flags = mlx4_en_get_priv_flags,
> + .get_tunable = mlx4_en_get_tunable,
> + .set_tunable = mlx4_en_set_tunable,
If the above initializers aren't aligned with tabs, why should these two be?
WBR, Sergei
--
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