From: Leon Romanovsky <leon@kernel.org>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: Ido Schimmel <idosch@idosch.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v4] net: psample: Introduce stubs to remove NIC driver dependency
Date: Tue, 9 Feb 2021 12:01:19 +0200 [thread overview]
Message-ID: <20210209100119.GC139298@unreal> (raw)
In-Reply-To: <CAJ3xEMh72mb9ZYd8umr-FTEO+MV6TNyqST2kLAz_wdLgPcFnww@mail.gmail.com>
On Tue, Feb 09, 2021 at 11:25:33AM +0200, Or Gerlitz wrote:
> On Tue, Feb 9, 2021 at 8:49 AM Leon Romanovsky <leon@kernel.org> wrote:
>
> [..]
>
> > This is another problem with mlx5 - complete madness with config options
> > that are not possible to test.
> > ➜ kernel git:(rdma-next) grep -h "config MLX" drivers/net/ethernet/mellanox/mlx5/core/Kconfig | awk '{ print $2}' | sort |uniq |wc -l
> > 19
>
> wait, why do you call it madness? we were suggested by some users (do
> git blame for the patches) to refine things with multiple configs and it seem
> to work quite well -- what you don't like? and what's wrong with simple grep..
Yes, I aware of these users and what and why they asked it.
They didn't ask us to have new config for every feature/file, but to have
light ethernet device.
Other users are distributions and they enable all options that supported in
the specific kernel they picked, because they don't know in advance where their
distro will be used.
You also don't have capacity to test various combinations, so you
test only small subset of common ones that are pretty standard. This is why
you have this feeling of "work quite well".
And I'm not talking about compilations but actual regression runs.
I suggest to reduce number of configs to small amount, something like 3-5 options:
* Basic ethernet driver
* + ETH
* + RDMA
* + VDPA
* ....
* Full mlx5 driver
And there is nothing wrong with simple grep, it was my copy/paste from
another internal thread where this config bloat caused us to some griefs
in regression.
Thanks
>
> $ grep "config MLX5_" drivers/net/ethernet/mellanox/mlx5/core/Kconfig
> config MLX5_CORE
> config MLX5_ACCEL
> config MLX5_FPGA
> config MLX5_CORE_EN
> config MLX5_EN_ARFS
> config MLX5_EN_RXNFC
> config MLX5_MPFS
> config MLX5_ESWITCH
> config MLX5_CLS_ACT
> config MLX5_TC_CT
> config MLX5_CORE_EN_DCB
> config MLX5_CORE_IPOIB
> config MLX5_FPGA_IPSEC
> config MLX5_IPSEC
> config MLX5_EN_IPSEC
> config MLX5_FPGA_TLS
> config MLX5_TLS
> config MLX5_EN_TLS
> config MLX5_SW_STEERING
> config MLX5_SF
> config MLX5_SF_MANAGER
> config MLX5_EN_NVMEOTCP
next prev parent reply other threads:[~2021-02-09 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 1:45 [PATCH net-next v4] net: psample: Introduce stubs to remove NIC driver dependency Chris Mi
2021-01-29 5:14 ` Cong Wang
2021-01-29 6:08 ` Chris Mi
2021-01-29 20:30 ` Jakub Kicinski
2021-01-29 20:44 ` Saeed Mahameed
2021-01-29 21:47 ` Jakub Kicinski
2021-01-30 14:42 ` Ido Schimmel
2021-02-01 1:37 ` Chris Mi
2021-02-01 18:08 ` Ido Schimmel
2021-02-08 7:03 ` Leon Romanovsky
2021-02-08 8:57 ` Ido Schimmel
2021-02-08 9:07 ` Leon Romanovsky
2021-02-08 17:07 ` Ido Schimmel
2021-02-09 6:47 ` Leon Romanovsky
2021-02-09 9:25 ` Or Gerlitz
2021-02-09 10:01 ` Leon Romanovsky [this message]
2021-02-09 10:49 ` Or Gerlitz
2021-02-11 5:09 ` Saeed Mahameed
2021-02-11 21:59 ` Ido Schimmel
2021-02-12 0:41 ` Saeed Mahameed
2021-01-29 21:50 ` Jakub Kicinski
2021-01-30 2:35 ` Chris Mi
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=20210209100119.GC139298@unreal \
--to=leon@kernel.org \
--cc=gerlitz.or@gmail.com \
--cc=idosch@idosch.org \
--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;
as well as URLs for NNTP newsgroup(s).