patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Jingjing Wu" <jingjing.wu@intel.com>, <dev@dpdk.org>
Cc: <beilei.xing@intel.com>, <stable@dpdk.org>
Subject: RE: [PATCH] net/idpf: fix build option check
Date: Thu, 8 Dec 2022 08:46:16 +0100	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87571@smartserver.smartshare.dk> (raw)
In-Reply-To: <20221208033127.57161-1-jingjing.wu@intel.com>

> From: Jingjing Wu [mailto:jingjing.wu@intel.com]
> Sent: Thursday, 8 December 2022 04.31
> 
> When enable_iova_as_pa option is disabled, idpf driver should avoid
> the building in its build file.
> 
> Fixes: 5bf87b45b2c8 (net/idpf: add AVX512 data path for single queue
> model)
> Cc: stable@dpdk.org
> 
> Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
> ---
>  drivers/net/idpf/meson.build | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/net/idpf/meson.build
> b/drivers/net/idpf/meson.build
> index 998afd21fe..650dade0b9 100644
> --- a/drivers/net/idpf/meson.build
> +++ b/drivers/net/idpf/meson.build
> @@ -7,6 +7,12 @@ if is_windows
>      subdir_done()
>  endif
> 
> +if dpdk_conf.get('RTE_IOVA_AS_PA') == 0
> +    build = false
> +    reason = 'driver does not support disabling IOVA as PA mode'
> +    subdir_done()
> +endif
> +
>  deps += ['common_idpf']
> 
>  sources = files(
> --
> 2.25.1
> 

I had to try the same, so I can surely say...

Reviewed-by: Morten Brørup <mb@smartsharesystems.com>


  reply	other threads:[~2022-12-08  7:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  3:31 Jingjing Wu
2022-12-08  7:46 ` Morten Brørup [this message]
2022-12-09  3:15 ` Xing, Beilei
2022-12-13  1:52   ` Zhang, Qi Z
2023-02-17 22:34     ` Thomas Monjalon
2023-02-19 10:52       ` Thomas Monjalon

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=98CBD80474FA8B44BF855DF32C47DC35D87571@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=stable@dpdk.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).