From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] net/idpf: fix build option check
Date: Fri, 9 Dec 2022 03:15:18 +0000 [thread overview]
Message-ID: <LV2PR11MB5997CA5C816579D18E150B99F71C9@LV2PR11MB5997.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221208033127.57161-1-jingjing.wu@intel.com>
> -----Original Message-----
> From: Wu, Jingjing <jingjing.wu@intel.com>
> Sent: Thursday, December 8, 2022 11:31 AM
> To: dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> stable@dpdk.org
> Subject: [PATCH] net/idpf: fix build option check
>
> 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
Acked-by: Beilei Xing <beilei.xing@intel.com>
next prev parent reply other threads:[~2022-12-09 3:15 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
2022-12-09 3:15 ` Xing, Beilei [this message]
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=LV2PR11MB5997CA5C816579D18E150B99F71C9@LV2PR11MB5997.namprd11.prod.outlook.com \
--to=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).