netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Kubecek <mkubecek@suse.cz>
To: netdev@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
	davem@davemloft.net, andrew@lunn.ch, ecree@solarflare.com,
	thomas.lendacky@amd.com, benve@cisco.com, _govind@gmx.com,
	peppe.cavallaro@st.com, alexandre.torgue@st.com,
	joabreu@synopsys.com, snelson@pensando.io,
	yisen.zhuang@huawei.com, salil.mehta@huawei.com,
	jeffrey.t.kirsher@intel.com, jacob.e.keller@intel.com,
	alexander.h.duyck@linux.intel.com, michael.chan@broadcom.com,
	saeedm@mellanox.com, leon@kernel.org
Subject: Re: [PATCH net-next v3 01/12] ethtool: add infrastructure for centralized checking of coalescing parameters
Date: Thu, 5 Mar 2020 14:13:01 +0100	[thread overview]
Message-ID: <20200305131301.GN4264@unicorn.suse.cz> (raw)
In-Reply-To: <20200305051542.991898-2-kuba@kernel.org>

On Wed, Mar 04, 2020 at 09:15:31PM -0800, Jakub Kicinski wrote:
> Linux supports 22 different interrupt coalescing parameters.
> No driver implements them all. Some drivers just ignore the
> ones they don't support, while others have to carry a long
> list of checks to reject unsupported settings.
> 
> To simplify the drivers add the ability to specify inside
> ethtool_ops which parameters are supported and let the core
> reject attempts to set any other one.
> 
> This commit makes the mechanism an opt-in, only drivers which
> set ethtool_opts->coalesce_types to a non-zero value will have
> the checks enforced.
> 
> The same mask is used for global and per queue settings.
> 
> v3: - move the (temporary) check if driver defines types
>       earlier (Michal)
>     - rename used_types -> nonzero_params, and
>       coalesce_types -> supported_coalesce_params (Alex)
>     - use EOPNOTSUPP instead of EINVAL (Andrew, Michal)
> 
> Leaving the long series of ifs for now, it seems nice to
> be able to grep for the field and flag names. This will
> probably have to be revisited once netlink support lands.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> ---

Reviewed-by: Michal Kubecek <mkubecek@suse.cz>

  reply	other threads:[~2020-03-05 13:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  5:15 [PATCH net-next v3 00/12] ethtool: consolidate parameter checking for irq coalescing Jakub Kicinski
2020-03-05  5:15 ` [PATCH net-next v3 01/12] ethtool: add infrastructure for centralized checking of coalescing parameters Jakub Kicinski
2020-03-05 13:13   ` Michal Kubecek [this message]
2020-03-05 13:27   ` Andrew Lunn
2020-03-05 16:24   ` Alexander Duyck
2020-03-05  5:15 ` [PATCH net-next v3 02/12] xgbe: let core reject the unsupported " Jakub Kicinski
2020-03-05 14:30   ` Tom Lendacky
2020-03-05  5:15 ` [PATCH net-next v3 03/12] enic: " Jakub Kicinski
2020-03-05  5:15 ` [PATCH net-next v3 04/12] stmmac: " Jakub Kicinski
2020-03-05  5:15 ` [PATCH net-next v3 05/12] nfp: " Jakub Kicinski
2020-03-05  5:15 ` [PATCH net-next v3 06/12] ionic: " Jakub Kicinski
2020-03-05  5:15 ` [PATCH net-next v3 07/12] hisilicon: " Jakub Kicinski
2020-03-05  5:15 ` [PATCH net-next v3 08/12] ice: " Jakub Kicinski
2020-03-05  5:15 ` [PATCH net-next v3 09/12] bnxt: reject unsupported coalescing params Jakub Kicinski
2020-03-05  5:15 ` [PATCH net-next v3 10/12] mlx5: " Jakub Kicinski
2020-03-05  8:14   ` Saeed Mahameed
2020-03-05  5:15 ` [PATCH net-next v3 11/12] e1000e: " Jakub Kicinski
2020-03-05  5:15 ` [PATCH net-next v3 12/12] virtio_net: " Jakub Kicinski
2020-03-05 20:17 ` [PATCH net-next v3 00/12] ethtool: consolidate parameter checking for irq coalescing 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=20200305131301.GN4264@unicorn.suse.cz \
    --to=mkubecek@suse.cz \
    --cc=_govind@gmx.com \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=alexandre.torgue@st.com \
    --cc=andrew@lunn.ch \
    --cc=benve@cisco.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=jacob.e.keller@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=joabreu@synopsys.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=saeedm@mellanox.com \
    --cc=salil.mehta@huawei.com \
    --cc=snelson@pensando.io \
    --cc=thomas.lendacky@amd.com \
    --cc=yisen.zhuang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).