netdev - Re: [PATCH net-next 2/2] add one config to select relax order mode in intel NIC's Kconfig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKgT0UdxwTDwSsHKj5GfWTdNOcPdsnHBeM0mDxGoifDr8G1DYQ@mail.gmail.com>
Date:   Fri, 3 Feb 2017 08:43:08 -0800
From:   Alexander Duyck <alexander.duyck@...il.com>
To:     Mao Wenan <maowenan@...wei.com>
Cc:     Netdev <netdev@...r.kernel.org>,
        Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Subject: Re: [PATCH net-next 2/2] add one config to select relax order mode in
 intel NIC's Kconfig

On Fri, Feb 3, 2017 at 1:30 AM, Mao Wenan <maowenan@...wei.com> wrote:
> This patch allows one to enable relax order mode in intel NIC's
> Kconfig. CONFIG_ARCH_WANT_RELAX_ORDER is a common macro for some
> CPU architecture to use relax order mode in NIC's source codes.
> CONFIG_ARCH_WANT_RELAX_ORDER can be defined in arch/xxx/Kconfig,
> such as sparc system exists in arch/sparc/Kconfig, but not all
> of arm64 systems can use relax order mode, so it can't be defined
> in arch/arm64/Kconfig. Therefore PCI_RELAX_ORDER in NIC's Kconfig
> provide one way to define macro CONFIG_ARCH_WANT_RELAX_ORDER.
>
> Signed-off-by: Mao Wenan <maowenan@...wei.com>
> ---
>  drivers/net/ethernet/intel/Kconfig | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
>
> diff --git a/drivers/net/ethernet/intel/Kconfig b/drivers/net/ethernet/intel/Kconfig
> index 1349b45..b366722 100644
> --- a/drivers/net/ethernet/intel/Kconfig
> +++ b/drivers/net/ethernet/intel/Kconfig
> @@ -275,4 +275,19 @@ config FM10K
>           To compile this driver as a module, choose M here. The module
>           will be called fm10k.  MSI-X interrupt support is required
>
> +config PCI_RELAX_ORDER
> +        bool "PCI relax order mode support"
> +        default n
> +        select ARCH_WANT_RELAX_ORDER
> +        ---help---
> +          This allows one to enable relax order mode in driver.
> +          CONFIG_ARCH_WANT_RELAX_ORDER is a common macro for some
> +          CPU architecture to use relax order mode in NIC's source codes.
> +          CONFIG_ARCH_WANT_RELAX_ORDER can be defined in arch/xxx/Kconfig,
> +          such as sparc system exists in arch/sparc/Kconfig, but not all
> +          of arm64 systems can use relax order mode, so it can't be defined
> +          in arch/arm64/Kconfig. Therefore PCI_RELAX_ORDER provide one way
> +          to define macro CONFIG_ARCH_WANT_RELAX_ORDER. Say Y here if you
> +          want to enable relax order.
> +
>  endif # NET_VENDOR_INTEL


You can't be dropping configuration options like this in here.  The
ARCH_WANT_RELAX_ORDER should be selected by the architecture as a
def_bool, not by the user via a kconfig option.  In addition this
option has no business in the Intel wired LAN directory as this
impacts all architectures.

This is something that would be an architecture specific PCI option
and could impact other PCI devices beyond what is just in networking.
If you are wanting to target the arm64 architecture you should
probably drop this in the /arch/arm64/Kconfig, then that way anyone
familiar with the arm64 hardware can chime in if enabling relaxed
ordering causes any known issues.

- Alex