From: Tal Shnaiderman <talshn@nvidia.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Asaf Penso <asafp@nvidia.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Eilon Greenstein <eilong@nvidia.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH 5/5] crypto/mlx5: support on Windows
Date: Sun, 17 Oct 2021 08:15:15 +0000 [thread overview]
Message-ID: <DM4PR12MB5389F44AD12421103AE5C4D5A4BB9@DM4PR12MB5389.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB448403DE524257BBBEB2EE24D8BA9@CO6PR18MB4484.namprd18.prod.outlook.com>
> Subject: RE: [EXT] [PATCH 5/5] crypto/mlx5: support on Windows
>
> External email: Use caution opening links or attachments
>
>
> > Add support for mlx5 crypto pmd on Windows OS.
> > Add changes to release note and pmd guide.
> >
> > Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
> > ---
> > doc/guides/cryptodevs/mlx5.rst | 15 ++++++++++++---
> > doc/guides/rel_notes/release_21_11.rst | 1 +
> > drivers/common/mlx5/version.map | 2 +-
> > drivers/common/mlx5/windows/mlx5_common_os.c | 2 +-
> > drivers/crypto/aesni_gcm/meson.build | 6 ++++++
> > drivers/crypto/aesni_mb/meson.build | 6 ++++++
> > drivers/crypto/armv8/meson.build | 6 ++++++
> > drivers/crypto/bcmfs/meson.build | 6 ++++++
> > drivers/crypto/ccp/meson.build | 1 +
> > drivers/crypto/kasumi/meson.build | 6 ++++++
> > drivers/crypto/meson.build | 3 ---
> > drivers/crypto/mlx5/meson.build | 4 ++--
> > drivers/crypto/mvsam/meson.build | 6 ++++++
> > drivers/crypto/null/meson.build | 6 ++++++
> > drivers/crypto/octeontx/meson.build | 6 ++++++
> > drivers/crypto/openssl/meson.build | 6 ++++++
> > drivers/crypto/qat/meson.build | 6 ++++++
> > drivers/crypto/scheduler/meson.build | 6 ++++++
> > drivers/crypto/snow3g/meson.build | 6 ++++++
> > drivers/crypto/virtio/meson.build | 6 ++++++
> > drivers/crypto/zuc/meson.build | 6 ++++++
> > 21 files changed, 102 insertions(+), 10 deletions(-)
> >
>
> Please split this patch into two
> - one for all drivers meson.build changes and
> - one for enabling Windows compilation for mlx5.
Sure, I'll split and send a v2.
prev parent reply other threads:[~2021-10-17 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 15:53 [dpdk-dev] [PATCH 0/5] Support MLX5 crypto driver " Tal Shnaiderman
2021-10-12 15:53 ` [dpdk-dev] [PATCH 1/5] common/mlx5: add DV enums to Windows defs file Tal Shnaiderman
2021-10-12 15:53 ` [dpdk-dev] [PATCH 2/5] crypto/mlx5: replace UNIX functions with EAL functions Tal Shnaiderman
2021-10-12 15:53 ` [dpdk-dev] [PATCH 3/5] crypto/mlx5: use OS agnostic functions for UMEM operations Tal Shnaiderman
2021-10-12 15:53 ` [dpdk-dev] [PATCH 4/5] crypto/mlx5: fix size of UMR WQE Tal Shnaiderman
2021-10-12 15:53 ` [dpdk-dev] [PATCH 5/5] crypto/mlx5: support on Windows Tal Shnaiderman
2021-10-16 15:05 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-17 8:15 ` Tal Shnaiderman [this message]
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=DM4PR12MB5389F44AD12421103AE5C4D5A4BB9@DM4PR12MB5389.namprd12.prod.outlook.com \
--to=talshn@nvidia.com \
--cc=asafp@nvidia.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=eilong@nvidia.com \
--cc=gakhil@marvell.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).