| Message ID | 20221008083747.6559-1-zhangfei.gao@linaro.org (mailing list archive) |
|---|---|
| Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 805E5A0542; Sat, 8 Oct 2022 10:38:48 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 26C3340146; Sat, 8 Oct 2022 10:38:48 +0200 (CEST) Received: from mail-pf1-f171.google.com (mail-pf1-f171.google.com [209.85.210.171]) by mails.dpdk.org (Postfix) with ESMTP id EFEB340042 for <dev@dpdk.org>; Sat, 8 Oct 2022 10:38:46 +0200 (CEST) Received: by mail-pf1-f171.google.com with SMTP id d10so6792680pfh.6 for <dev@dpdk.org>; Sat, 08 Oct 2022 01:38:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=+/haNPWatod3MjWbSogUWyplF22bQkGBXrJBqQawGtQ=; b=gK+uw+Ba1jVFMXIVEQKnwrM5KULiJxPP9ScN8hPKpGcLjJ3MG1wbocWFu8h/2rY+BH MSvtfSD0X/rw4kUmLZsS2Sie7YP0aYHokmob9BH9AwdUTntsKdsrs56bhxkoC8NSqW/A uuq42NlwocsVe6wD//8c/T8pe8WI+uVqw/AxlZHWkouAjP5OCLZg+gKeu+ZsDPU7ot4V wT5sY6Zj7JH5gIF0NLy3lSyq0xWH9brus07zdhKX1hH6u8nEqgAIOWZTYK5Tr7Nc8M4z Y9a/wiMkSYE57JyyXDgassePYuhC5FHUzRehQ+rvoZ7jpsxsucTOWPVCcIH6hrG/44kv Osuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+/haNPWatod3MjWbSogUWyplF22bQkGBXrJBqQawGtQ=; b=g2asSBeA1Q82O6iG618/ZLogcxCItThKxKf5uTIrmCGv39hp4J2/gckZx5cG8Xe+F+ MnnKgRBFiN0L0+O8FNZhb7lbE3Opgpl7c6DCf9rNF1eBCQJhEFsYNK6hKvt5Qli4F7Xz hmQMOd/IIqJa6XdiF3gymINnUhPqye2NQNd90qx4hUdohriTb8FGorNN3GarERKeYkkM 1LiNJPdudiORkcdS9xdEM6JqxVVlxmUonQQxXLPv8FTkxBlb5XGoOHYDhAfrSJGLVhis we+P73NiiMweOvALR6q1XZSKZuoeBAQxGezJH6fecGNJA5cTP2JvuHSFrLMBqqSuVGGA UXGw== X-Gm-Message-State: ACrzQf1ti7TuzB6MxNYry5c5exw8Fs7rt12i7q/aTLUmAstQFPcDcXLp 5v5rxe4P1Wn/mXgbapw3ePnOoA== X-Google-Smtp-Source: AMsMyM6cza8Uhe6qi7uGS4o/XGxkujN8eFc8nc6rtlj2yeJQ5Zrjt7wgHqWLFIY4m8QBfrjBF8fsOg== X-Received: by 2002:a63:5762:0:b0:43c:c1b5:3e75 with SMTP id h34-20020a635762000000b0043cc1b53e75mr7874114pgm.380.1665218326066; Sat, 08 Oct 2022 01:38:46 -0700 (PDT) Received: from localhost.localdomain ([194.5.48.65]) by smtp.gmail.com with ESMTPSA id n1-20020a17090a2bc100b0020a0571b354sm2644371pje.57.2022.10.08.01.38.41 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Oct 2022 01:38:45 -0700 (PDT) From: Zhangfei Gao <zhangfei.gao@linaro.org> To: Akhil Goyal <gakhil@marvell.com>, Declan Doherty <declan.doherty@intel.com>, Fan Zhang <roy.fan.zhang@intel.com>, Ashish Gupta <ashish.gupta@marvell.com>, Ray Kinsella <mdr@ashroe.eu> Cc: dev@dpdk.org, acc@openeuler.org, Zhangfei Gao <zhangfei.gao@linaro.org> Subject: [PATCH resend v3 0/6] crypto/uadk: introduce uadk crypto driver Date: Sat, 8 Oct 2022 16:37:41 +0800 Message-Id: <20221008083747.6559-1-zhangfei.gao@linaro.org> X-Mailer: git-send-email 2.36.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org |
| Series |
crypto/uadk: introduce uadk crypto driver
|
|
Message
Zhangfei Gao
Oct. 8, 2022, 8:37 a.m. UTC
Introduce a new crypto PMD for hardware accelerators based on UADK [1].
UADK is a framework for user applications to access hardware accelerators.
UADK relies on IOMMU SVA (Shared Virtual Address) feature, which share
the same page table between IOMMU and MMU.
Thereby user application can directly use virtual address for device dma,
which enhances the performance as well as easy usability.
[1] https://github.com/Linaro/uadk
Test:
sudo dpdk-test --vdev=crypto_uadk (--log-level=6)
RTE>>cryptodev_uadk_autotest
RTE>>quit
resend:
Rebase on next/for-main, which just merged series "cryptodev: rework session framework".
update in v3:
Split patches according to Akhil's suggestions
Please split the patches as below.
1. introduce driver - create files with meson.build and with probe/remove
and device ops defined but not implemented. You do not need to write empty functions.
Add basic documentation also which defines what the driver is.
You can explain the build dependency here.
2. define queue structs and setup/remove APIs
3. Add data path
4. implement cipher op. Add capabilities and documentation of what is supported in each of the patch. Add feature flags etc.
5. implement auth, add capabilities and documentation
6. test app changes.
Update in v2:
Change uadk_supported_platform to uadk_crypto_version, which matches better
than platform.
enum uadk_crypto_version {
UADK_CRYPTO_V2,
UADK_CRYPTO_V3,
};
Update in v1, compared with rfc
Suggested from Akhil Goyal <gakhil@marvell.com>
Only consider crypto PMD first
Split patch into small (individually compiled) patches.
Update MAINTAINERS and doc/guides/cryptodevs/features/uadk.ini
Zhangfei Gao (6):
crypto/uadk: introduce uadk crypto driver
crypto/uadk: support basic operations
crypto/uadk: support enqueue/dequeue operations
crypto/uadk: support cipher algorithms
crypto/uadk: support auth algorithms
test/crypto: add cryptodev_uadk_autotest
MAINTAINERS | 6 +
app/test/test_cryptodev.c | 7 +
app/test/test_cryptodev.h | 1 +
doc/guides/cryptodevs/features/uadk.ini | 55 ++
doc/guides/cryptodevs/index.rst | 1 +
doc/guides/cryptodevs/uadk.rst | 74 ++
drivers/crypto/meson.build | 1 +
drivers/crypto/uadk/meson.build | 36 +
drivers/crypto/uadk/uadk_crypto_pmd.c | 1145 +++++++++++++++++++++++
drivers/crypto/uadk/version.map | 3 +
10 files changed, 1329 insertions(+)
create mode 100644 doc/guides/cryptodevs/features/uadk.ini
create mode 100644 doc/guides/cryptodevs/uadk.rst
create mode 100644 drivers/crypto/uadk/meson.build
create mode 100644 drivers/crypto/uadk/uadk_crypto_pmd.c
create mode 100644 drivers/crypto/uadk/version.map
Comments
Hi Zhangfei,
I see below compilation error after executing the steps mentioned in UADK README. It would be better if you could add compilation steps for UADK in uadk.rst as well.
gakhil@cavium-SR1-T640:/home/gakhil/up/uadk$ make
make all-recursive
make[1]: Entering directory '/home/gakhil/up/uadk'
Making all in .
make[2]: Entering directory '/home/gakhil/up/uadk'
depbase=`echo wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
/bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include -DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" -DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD -MP -MF $depbase.Tpo -c -o wd.lo wd.c &&\
mv -f $depbase.Tpo $depbase.Plo
libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "-DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD -MP -MF .deps/wd.Tpo -c wd.c -fPIC -DPIC -o .libs/wd.o
depbase=`echo wd_mempool.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
/bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include -DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" -DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd_mempool.lo -MD -MP -MF $depbase.Tpo -c -o wd_mempool.lo wd_mempool.c &&\
mv -f $depbase.Tpo $depbase.Plo
libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "-DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd_mempool.lo -MD -MP -MF .deps/wd_mempool.Tpo -c wd_mempool.c -fPIC -DPIC -o .libs/wd_mempool.o
depbase=`echo v1/wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
/bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include -DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" -DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo -MD -MP -MF $depbase.Tpo -c -o v1/wd.lo v1/wd.c &&\
mv -f $depbase.Tpo $depbase.Plo
libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "-DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo -MD -MP -MF v1/.deps/wd.Tpo -c v1/wd.c -fPIC -DPIC -o v1/.libs/wd.o
In file included from v1/wd.c:30:
./v1/wd_util.h:354:2: error: #error "no platform mb, define one before compiling"
354 | #error "no platform mb, define one before compiling"
| ^~~~~
make[2]: *** [Makefile:788: v1/wd.lo] Error 1
make[2]: Leaving directory '/home/gakhil/up/uadk'
make[1]: *** [Makefile:859: all-recursive] Error 1
make[1]: Leaving directory '/home/gakhil/up/uadk'
make: *** [Makefile:565: all] Error 2
> -----Original Message-----
> From: Zhangfei Gao <zhangfei.gao@linaro.org>
> Sent: Saturday, October 8, 2022 2:08 PM
> To: Akhil Goyal <gakhil@marvell.com>; Declan Doherty
> <declan.doherty@intel.com>; Fan Zhang <roy.fan.zhang@intel.com>; Ashish
> Gupta <ashishg@marvell.com>; Ray Kinsella <mdr@ashroe.eu>
> Cc: dev@dpdk.org; acc@openeuler.org; Zhangfei Gao
> <zhangfei.gao@linaro.org>
> Subject: [EXT] [PATCH resend v3 0/6] crypto/uadk: introduce uadk crypto driver
>
> External Email
>
> ----------------------------------------------------------------------
> Introduce a new crypto PMD for hardware accelerators based on UADK [1].
>
> UADK is a framework for user applications to access hardware accelerators.
> UADK relies on IOMMU SVA (Shared Virtual Address) feature, which share
> the same page table between IOMMU and MMU.
> Thereby user application can directly use virtual address for device dma,
> which enhances the performance as well as easy usability.
>
> [1] https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_Linaro_uadk&d=DwIDAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=Dn
> L7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m=riOYJQEEoq2hZSApJn-
> _dXs6fqKRm8wqS-cJ48j15-
> zpW3dOS8NrcrsBD7wC4cqY&s=irxZ2g1W2PchLQnfMPsNb8WJpjCS_-
> Y_sdVRQT6wwo0&e=
>
> Test:
> sudo dpdk-test --vdev=crypto_uadk (--log-level=6)
> RTE>>cryptodev_uadk_autotest
> RTE>>quit
>
> resend:
> Rebase on next/for-main, which just merged series "cryptodev: rework session
> framework".
>
> update in v3:
> Split patches according to Akhil's suggestions
> Please split the patches as below.
> 1. introduce driver - create files with meson.build and with probe/remove
> and device ops defined but not implemented. You do not need to write empty
> functions.
> Add basic documentation also which defines what the driver is.
> You can explain the build dependency here.
> 2. define queue structs and setup/remove APIs
> 3. Add data path
> 4. implement cipher op. Add capabilities and documentation of what is
> supported in each of the patch. Add feature flags etc.
> 5. implement auth, add capabilities and documentation
> 6. test app changes.
>
> Update in v2:
> Change uadk_supported_platform to uadk_crypto_version, which matches
> better
> than platform.
> enum uadk_crypto_version {
> UADK_CRYPTO_V2,
> UADK_CRYPTO_V3,
> };
>
> Update in v1, compared with rfc
>
> Suggested from Akhil Goyal <gakhil@marvell.com>
> Only consider crypto PMD first
> Split patch into small (individually compiled) patches.
> Update MAINTAINERS and doc/guides/cryptodevs/features/uadk.ini
>
> Zhangfei Gao (6):
> crypto/uadk: introduce uadk crypto driver
> crypto/uadk: support basic operations
> crypto/uadk: support enqueue/dequeue operations
> crypto/uadk: support cipher algorithms
> crypto/uadk: support auth algorithms
> test/crypto: add cryptodev_uadk_autotest
>
> MAINTAINERS | 6 +
> app/test/test_cryptodev.c | 7 +
> app/test/test_cryptodev.h | 1 +
> doc/guides/cryptodevs/features/uadk.ini | 55 ++
> doc/guides/cryptodevs/index.rst | 1 +
> doc/guides/cryptodevs/uadk.rst | 74 ++
> drivers/crypto/meson.build | 1 +
> drivers/crypto/uadk/meson.build | 36 +
> drivers/crypto/uadk/uadk_crypto_pmd.c | 1145 +++++++++++++++++++++++
> drivers/crypto/uadk/version.map | 3 +
> 10 files changed, 1329 insertions(+)
> create mode 100644 doc/guides/cryptodevs/features/uadk.ini
> create mode 100644 doc/guides/cryptodevs/uadk.rst
> create mode 100644 drivers/crypto/uadk/meson.build
> create mode 100644 drivers/crypto/uadk/uadk_crypto_pmd.c
> create mode 100644 drivers/crypto/uadk/version.map
>
> --
> 2.36.1
On 2022/10/10 下午3:55, Akhil Goyal wrote: > Hi Zhangfei, > > I see below compilation error after executing the steps mentioned in UADK README. It would be better if you could add compilation steps for UADK in uadk.rst as well. Sure Will add something like this Build & Install UADK on ARM -------------------- ``` git clone https://github.com/Linaro/uadk.git cd uadk ./cleanup.sh ./autogen.sh ./conf.sh make sudo make install ``` * If get error:"cannot find -lnuma", please install the libnuma-dev > > gakhil@cavium-SR1-T640:/home/gakhil/up/uadk$ make > make all-recursive > make[1]: Entering directory '/home/gakhil/up/uadk' > Making all in . > make[2]: Entering directory '/home/gakhil/up/uadk' > depbase=`echo wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include -DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" -DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD -MP -MF $depbase.Tpo -c -o wd.lo wd.c &&\ > mv -f $depbase.Tpo $depbase.Plo > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "-DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD -MP -MF .deps/wd.Tpo -c wd.c -fPIC -DPIC -o .libs/wd.o > depbase=`echo wd_mempool.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include -DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" -DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd_mempool.lo -MD -MP -MF $depbase.Tpo -c -o wd_mempool.lo wd_mempool.c &&\ > mv -f $depbase.Tpo $depbase.Plo > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "-DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd_mempool.lo -MD -MP -MF .deps/wd_mempool.Tpo -c wd_mempool.c -fPIC -DPIC -o .libs/wd_mempool.o > depbase=`echo v1/wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include -DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" -DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo -MD -MP -MF $depbase.Tpo -c -o v1/wd.lo v1/wd.c &&\ > mv -f $depbase.Tpo $depbase.Plo > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing -I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "-DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo -MD -MP -MF v1/.deps/wd.Tpo -c v1/wd.c -fPIC -DPIC -o v1/.libs/wd.o > In file included from v1/wd.c:30: > ./v1/wd_util.h:354:2: error: #error "no platform mb, define one before compiling" > 354 | #error "no platform mb, define one before compiling" > | ^~~~~ > make[2]: *** [Makefile:788: v1/wd.lo] Error 1 > make[2]: Leaving directory '/home/gakhil/up/uadk' > make[1]: *** [Makefile:859: all-recursive] Error 1 > make[1]: Leaving directory '/home/gakhil/up/uadk' > make: *** [Makefile:565: all] Error 2 By the way, what platform are you using. I can not reproduce this error. Thanks
> > gakhil@cavium-SR1-T640:/home/gakhil/up/uadk$ make > > make all-recursive > > make[1]: Entering directory '/home/gakhil/up/uadk' > > Making all in . > > make[2]: Entering directory '/home/gakhil/up/uadk' > > depbase=`echo wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - > Wall -Werror -fno-strict-aliasing -I./include - > DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD - > MP -MF $depbase.Tpo -c -o wd.lo wd.c &&\ > > mv -f $depbase.Tpo $depbase.Plo > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing - > I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD -MP > -MF .deps/wd.Tpo -c wd.c -fPIC -DPIC -o .libs/wd.o > > depbase=`echo wd_mempool.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - > Wall -Werror -fno-strict-aliasing -I./include - > DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT > wd_mempool.lo -MD -MP -MF $depbase.Tpo -c -o wd_mempool.lo > wd_mempool.c &&\ > > mv -f $depbase.Tpo $depbase.Plo > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing - > I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT > wd_mempool.lo -MD -MP -MF .deps/wd_mempool.Tpo -c wd_mempool.c -fPIC > -DPIC -o .libs/wd_mempool.o > > depbase=`echo v1/wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - > Wall -Werror -fno-strict-aliasing -I./include - > DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo -MD > -MP -MF $depbase.Tpo -c -o v1/wd.lo v1/wd.c &&\ > > mv -f $depbase.Tpo $depbase.Plo > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-aliasing - > I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo -MD - > MP -MF v1/.deps/wd.Tpo -c v1/wd.c -fPIC -DPIC -o v1/.libs/wd.o > > In file included from v1/wd.c:30: > > ./v1/wd_util.h:354:2: error: #error "no platform mb, define one before > compiling" > > 354 | #error "no platform mb, define one before compiling" > > | ^~~~~ > > make[2]: *** [Makefile:788: v1/wd.lo] Error 1 > > make[2]: Leaving directory '/home/gakhil/up/uadk' > > make[1]: *** [Makefile:859: all-recursive] Error 1 > > make[1]: Leaving directory '/home/gakhil/up/uadk' > > make: *** [Makefile:565: all] Error 2 > By the way, what platform are you using. > I can not reproduce this error. > I am compiling on Intel XEON server with ubuntu 18.04
> > > gakhil@cavium-SR1-T640:/home/gakhil/up/uadk$ make > > > make all-recursive > > > make[1]: Entering directory '/home/gakhil/up/uadk' > > > Making all in . > > > make[2]: Entering directory '/home/gakhil/up/uadk' > > > depbase=`echo wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > > > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - > > Wall -Werror -fno-strict-aliasing -I./include - > > DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > > DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD - > > MP -MF $depbase.Tpo -c -o wd.lo wd.c &&\ > > > mv -f $depbase.Tpo $depbase.Plo > > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- > aliasing - > > I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > > DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD - > MP > > -MF .deps/wd.Tpo -c wd.c -fPIC -DPIC -o .libs/wd.o > > > depbase=`echo wd_mempool.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > > > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - > > Wall -Werror -fno-strict-aliasing -I./include - > > DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > > DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT > > wd_mempool.lo -MD -MP -MF $depbase.Tpo -c -o wd_mempool.lo > > wd_mempool.c &&\ > > > mv -f $depbase.Tpo $depbase.Plo > > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- > aliasing - > > I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > > DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT > > wd_mempool.lo -MD -MP -MF .deps/wd_mempool.Tpo -c wd_mempool.c - > fPIC > > -DPIC -o .libs/wd_mempool.o > > > depbase=`echo v1/wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > > > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - > > Wall -Werror -fno-strict-aliasing -I./include - > > DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > > DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo - > MD > > -MP -MF $depbase.Tpo -c -o v1/wd.lo v1/wd.c &&\ > > > mv -f $depbase.Tpo $depbase.Plo > > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- > aliasing - > > I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > > DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo - > MD - > > MP -MF v1/.deps/wd.Tpo -c v1/wd.c -fPIC -DPIC -o v1/.libs/wd.o > > > In file included from v1/wd.c:30: > > > ./v1/wd_util.h:354:2: error: #error "no platform mb, define one before > > compiling" > > > 354 | #error "no platform mb, define one before compiling" > > > | ^~~~~ > > > make[2]: *** [Makefile:788: v1/wd.lo] Error 1 > > > make[2]: Leaving directory '/home/gakhil/up/uadk' > > > make[1]: *** [Makefile:859: all-recursive] Error 1 > > > make[1]: Leaving directory '/home/gakhil/up/uadk' > > > make: *** [Makefile:565: all] Error 2 > > By the way, what platform are you using. > > I can not reproduce this error. > > > I am compiling on Intel XEON server with ubuntu 18.04 Any update??
Hi, Akhil On 2022/10/11 下午5:22, Akhil Goyal wrote: >>>> gakhil@cavium-SR1-T640:/home/gakhil/up/uadk$ make >>>> make all-recursive >>>> make[1]: Entering directory '/home/gakhil/up/uadk' >>>> Making all in . >>>> make[2]: Entering directory '/home/gakhil/up/uadk' >>>> depbase=`echo wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - >>> Wall -Werror -fno-strict-aliasing -I./include - >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD - >>> MP -MF $depbase.Tpo -c -o wd.lo wd.c &&\ >>>> mv -f $depbase.Tpo $depbase.Plo >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- >> aliasing - >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD - >> MP >>> -MF .deps/wd.Tpo -c wd.c -fPIC -DPIC -o .libs/wd.o >>>> depbase=`echo wd_mempool.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - >>> Wall -Werror -fno-strict-aliasing -I./include - >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT >>> wd_mempool.lo -MD -MP -MF $depbase.Tpo -c -o wd_mempool.lo >>> wd_mempool.c &&\ >>>> mv -f $depbase.Tpo $depbase.Plo >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- >> aliasing - >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT >>> wd_mempool.lo -MD -MP -MF .deps/wd_mempool.Tpo -c wd_mempool.c - >> fPIC >>> -DPIC -o .libs/wd_mempool.o >>>> depbase=`echo v1/wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - >>> Wall -Werror -fno-strict-aliasing -I./include - >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo - >> MD >>> -MP -MF $depbase.Tpo -c -o v1/wd.lo v1/wd.c &&\ >>>> mv -f $depbase.Tpo $depbase.Plo >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- >> aliasing - >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo - >> MD - >>> MP -MF v1/.deps/wd.Tpo -c v1/wd.c -fPIC -DPIC -o v1/.libs/wd.o >>>> In file included from v1/wd.c:30: >>>> ./v1/wd_util.h:354:2: error: #error "no platform mb, define one before >>> compiling" >>>> 354 | #error "no platform mb, define one before compiling" >>>> | ^~~~~ >>>> make[2]: *** [Makefile:788: v1/wd.lo] Error 1 >>>> make[2]: Leaving directory '/home/gakhil/up/uadk' >>>> make[1]: *** [Makefile:859: all-recursive] Error 1 >>>> make[1]: Leaving directory '/home/gakhil/up/uadk' >>>> make: *** [Makefile:565: all] Error 2 >>> By the way, what platform are you using. >>> I can not reproduce this error. >>> >> I am compiling on Intel XEON server with ubuntu 18.04 > Any update?? Looks the uadk library only considers ARM local build for some time. I am in checking how to cross-compile on x86. Sorry for the inconvenience. Thanks
Hi, Akhil On 2022/10/11 下午5:22, Akhil Goyal wrote: >>>> gakhil@cavium-SR1-T640:/home/gakhil/up/uadk$ make >>>> make all-recursive >>>> make[1]: Entering directory '/home/gakhil/up/uadk' >>>> Making all in . >>>> make[2]: Entering directory '/home/gakhil/up/uadk' >>>> depbase=`echo wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - >>> Wall -Werror -fno-strict-aliasing -I./include - >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD - >>> MP -MF $depbase.Tpo -c -o wd.lo wd.c &&\ >>>> mv -f $depbase.Tpo $depbase.Plo >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- >> aliasing - >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD - >> MP >>> -MF .deps/wd.Tpo -c wd.c -fPIC -DPIC -o .libs/wd.o >>>> depbase=`echo wd_mempool.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - >>> Wall -Werror -fno-strict-aliasing -I./include - >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT >>> wd_mempool.lo -MD -MP -MF $depbase.Tpo -c -o wd_mempool.lo >>> wd_mempool.c &&\ >>>> mv -f $depbase.Tpo $depbase.Plo >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- >> aliasing - >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT >>> wd_mempool.lo -MD -MP -MF .deps/wd_mempool.Tpo -c wd_mempool.c - >> fPIC >>> -DPIC -o .libs/wd_mempool.o >>>> depbase=`echo v1/wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - >>> Wall -Werror -fno-strict-aliasing -I./include - >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo - >> MD >>> -MP -MF $depbase.Tpo -c -o v1/wd.lo v1/wd.c &&\ >>>> mv -f $depbase.Tpo $depbase.Plo >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- >> aliasing - >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo - >> MD - >>> MP -MF v1/.deps/wd.Tpo -c v1/wd.c -fPIC -DPIC -o v1/.libs/wd.o >>>> In file included from v1/wd.c:30: >>>> ./v1/wd_util.h:354:2: error: #error "no platform mb, define one before >>> compiling" >>>> 354 | #error "no platform mb, define one before compiling" >>>> | ^~~~~ >>>> make[2]: *** [Makefile:788: v1/wd.lo] Error 1 >>>> make[2]: Leaving directory '/home/gakhil/up/uadk' >>>> make[1]: *** [Makefile:859: all-recursive] Error 1 >>>> make[1]: Leaving directory '/home/gakhil/up/uadk' >>>> make: *** [Makefile:565: all] Error 2 >>> By the way, what platform are you using. >>> I can not reproduce this error. >>> >> I am compiling on Intel XEON server with ubuntu 18.04 > Any update?? The uadk lib needs cross-compile on x86. Toolchain: https://releases.linaro.org/components/toolchain/binaries/latest-7/aarch64-linux-gnu/ Details are documented in https://github.com/Linaro/uadk/blob/master/INSTALL Considering the confusion caused by simple build info in README, We are planning to remove the simple build step in README, only keeps INSTALL. https://github.com/Linaro/uadk/pull/510 Since there are some dependent libraries (libz & openssl) causes cross-compile complicated. We are planning to omit build tests if not found these libs https://github.com/Linaro/uadk/pull/508 Only libnuma is must required for lib. Fortunately the numa cross compile is simple https://github.com/Linaro/uadk/blob/master/INSTALL $git clone https://github.com/numactl/numactl.git $cd numactl $./autogen.sh $autoconf -i $CC=aarch64-linux-gnu-gcc ./configure --host=i386-linux-gnu --target=aarch64-linux-gnu --prefix=${LIBROOT}/usr/local $make $make install Do you think we still need paste uadk build steps (and cross-compile steps) on dpdk doc/guides/cryptodevs/uadk.rst Sorry for the confusion. Thanks
Hi Zhangfei, > Hi, Akhil > > On 2022/10/11 下午5:22, Akhil Goyal wrote: > >>>> gakhil@cavium-SR1-T640:/home/gakhil/up/uadk$ make > >>>> make all-recursive > >>>> make[1]: Entering directory '/home/gakhil/up/uadk' > >>>> Making all in . > >>>> make[2]: Entering directory '/home/gakhil/up/uadk' > >>>> depbase=`echo wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > - > >>> Wall -Werror -fno-strict-aliasing -I./include - > >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo - > MD - > >>> MP -MF $depbase.Tpo -c -o wd.lo wd.c &&\ > >>>> mv -f $depbase.Tpo $depbase.Plo > >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- > >> aliasing - > >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo -MD > - > >> MP > >>> -MF .deps/wd.Tpo -c wd.c -fPIC -DPIC -o .libs/wd.o > >>>> depbase=`echo wd_mempool.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > - > >>> Wall -Werror -fno-strict-aliasing -I./include - > >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT > >>> wd_mempool.lo -MD -MP -MF $depbase.Tpo -c -o wd_mempool.lo > >>> wd_mempool.c &&\ > >>>> mv -f $depbase.Tpo $depbase.Plo > >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- > >> aliasing - > >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT > >>> wd_mempool.lo -MD -MP -MF .deps/wd_mempool.Tpo -c wd_mempool.c - > >> fPIC > >>> -DPIC -o .libs/wd_mempool.o > >>>> depbase=`echo v1/wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > - > >>> Wall -Werror -fno-strict-aliasing -I./include - > >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo > - > >> MD > >>> -MP -MF $depbase.Tpo -c -o v1/wd.lo v1/wd.c &&\ > >>>> mv -f $depbase.Tpo $depbase.Plo > >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- > >> aliasing - > >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo - > >> MD - > >>> MP -MF v1/.deps/wd.Tpo -c v1/wd.c -fPIC -DPIC -o v1/.libs/wd.o > >>>> In file included from v1/wd.c:30: > >>>> ./v1/wd_util.h:354:2: error: #error "no platform mb, define one before > >>> compiling" > >>>> 354 | #error "no platform mb, define one before compiling" > >>>> | ^~~~~ > >>>> make[2]: *** [Makefile:788: v1/wd.lo] Error 1 > >>>> make[2]: Leaving directory '/home/gakhil/up/uadk' > >>>> make[1]: *** [Makefile:859: all-recursive] Error 1 > >>>> make[1]: Leaving directory '/home/gakhil/up/uadk' > >>>> make: *** [Makefile:565: all] Error 2 > >>> By the way, what platform are you using. > >>> I can not reproduce this error. > >>> > >> I am compiling on Intel XEON server with ubuntu 18.04 > > Any update?? > The uadk lib needs cross-compile on x86. > Toolchain: > https://urldefense.proofpoint.com/v2/url?u=https- > 3A__releases.linaro.org_components_toolchain_binaries_latest-2D7_aarch64- > 2Dlinux- > 2Dgnu_&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=DnL7Si2wl_PRwpZ9TWey > 3eu68gBzn7DkPwuqhd6WNyo&m=91MX2Cs8jDO3kZ8m02cjnNdNxbSoW7V9DE > o6KPhTRzdWILxa_DQzYPoa5c5Lq9Q8&s=2- > jhckUNn9LCXbLaFaAEdl_5seC82SCXxvkVQEPnNz0&e= > Details are documented in https://urldefense.proofpoint.com/v2/url?u=https- > 3A__github.com_Linaro_uadk_blob_master_INSTALL&d=DwIDaQ&c=nKjWec2b > 6R0mOyPaz7xtfQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m > =91MX2Cs8jDO3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9 > Q8&s=pyjDRDPApEQXxPjZ4q0QlXT5DgmAAYdZtNscFbRp8lk&e= > > Considering the confusion caused by simple build info in README, > We are planning to remove the simple build step in README, only keeps > INSTALL. > https://urldefense.proofpoint.com/v2/url?u=https- > 3A__github.com_Linaro_uadk_pull_510&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7x > tfQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m=91MX2Cs8jD > O3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9Q8&s=m6I26 > VelKVBjODnByclMKGtmaSEN2kv8ACeZsWbPTg4&e= > > Since there are some dependent libraries (libz & openssl) causes > cross-compile complicated. > We are planning to omit build tests if not found these libs > https://urldefense.proofpoint.com/v2/url?u=https- > 3A__github.com_Linaro_uadk_pull_508&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7x > tfQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m=91MX2Cs8jD > O3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9Q8&s=tcbWSI > hyL8b2mX4-Ta54bR4kH2fNkezlmVD24I09mTc&e= > > Only libnuma is must required for lib. > Fortunately the numa cross compile is simple > > https://urldefense.proofpoint.com/v2/url?u=https- > 3A__github.com_Linaro_uadk_blob_master_INSTALL&d=DwIDaQ&c=nKjWec2b > 6R0mOyPaz7xtfQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m > =91MX2Cs8jDO3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9 > Q8&s=pyjDRDPApEQXxPjZ4q0QlXT5DgmAAYdZtNscFbRp8lk&e= > $git clone https://urldefense.proofpoint.com/v2/url?u=https- > 3A__github.com_numactl_numactl.git&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7xt > fQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m=91MX2Cs8jD > O3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9Q8&s=hZdhP > WLMGMgV9tP7nEQY1G_iWnODYJMCfR41whWchSU&e= > $cd numactl > $./autogen.sh > $autoconf -i > $CC=aarch64-linux-gnu-gcc ./configure --host=i386-linux-gnu > --target=aarch64-linux-gnu --prefix=${LIBROOT}/usr/local > $make > $make install > > Do you think we still need paste uadk build steps (and cross-compile steps) > on dpdk doc/guides/cryptodevs/uadk.rst > Is it not possible to use pkg-config? Also while building on DPDK which config file is needed? Do you need that also to be cross compiled?
> Hi Zhangfei, > > Hi, Akhil > > > > On 2022/10/11 下午5:22, Akhil Goyal wrote: > > >>>> gakhil@cavium-SR1-T640:/home/gakhil/up/uadk$ make > > >>>> make all-recursive > > >>>> make[1]: Entering directory '/home/gakhil/up/uadk' > > >>>> Making all in . > > >>>> make[2]: Entering directory '/home/gakhil/up/uadk' > > >>>> depbase=`echo wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > > >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H - > I. > > - > > >>> Wall -Werror -fno-strict-aliasing -I./include - > > >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > > >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo - > > MD - > > >>> MP -MF $depbase.Tpo -c -o wd.lo wd.c &&\ > > >>>> mv -f $depbase.Tpo $depbase.Plo > > >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- > > >> aliasing - > > >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > > >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT wd.lo - > MD > > - > > >> MP > > >>> -MF .deps/wd.Tpo -c wd.c -fPIC -DPIC -o .libs/wd.o > > >>>> depbase=`echo wd_mempool.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > > >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H - > I. > > - > > >>> Wall -Werror -fno-strict-aliasing -I./include - > > >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > > >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT > > >>> wd_mempool.lo -MD -MP -MF $depbase.Tpo -c -o wd_mempool.lo > > >>> wd_mempool.c &&\ > > >>>> mv -f $depbase.Tpo $depbase.Plo > > >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- > > >> aliasing - > > >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > > >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT > > >>> wd_mempool.lo -MD -MP -MF .deps/wd_mempool.Tpo -c wd_mempool.c > - > > >> fPIC > > >>> -DPIC -o .libs/wd_mempool.o > > >>>> depbase=`echo v1/wd.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > > >>>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H - > I. > > - > > >>> Wall -Werror -fno-strict-aliasing -I./include - > > >>> DUADK_VERSION_NUMBER="\"UADK version: 2.3.37\"" - > > >>> DUADK_RELEASED_TIME="\"Released Jun 11, 2022\"" -g -O2 -MT > v1/wd.lo > > - > > >> MD > > >>> -MP -MF $depbase.Tpo -c -o v1/wd.lo v1/wd.c &&\ > > >>>> mv -f $depbase.Tpo $depbase.Plo > > >>>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict- > > >> aliasing - > > >>> I./include "-DUADK_VERSION_NUMBER=\"UADK version: 2.3.37\"" "- > > >>> DUADK_RELEASED_TIME=\"Released Jun 11, 2022\"" -g -O2 -MT v1/wd.lo > - > > >> MD - > > >>> MP -MF v1/.deps/wd.Tpo -c v1/wd.c -fPIC -DPIC -o v1/.libs/wd.o > > >>>> In file included from v1/wd.c:30: > > >>>> ./v1/wd_util.h:354:2: error: #error "no platform mb, define one before > > >>> compiling" > > >>>> 354 | #error "no platform mb, define one before compiling" > > >>>> | ^~~~~ > > >>>> make[2]: *** [Makefile:788: v1/wd.lo] Error 1 > > >>>> make[2]: Leaving directory '/home/gakhil/up/uadk' > > >>>> make[1]: *** [Makefile:859: all-recursive] Error 1 > > >>>> make[1]: Leaving directory '/home/gakhil/up/uadk' > > >>>> make: *** [Makefile:565: all] Error 2 > > >>> By the way, what platform are you using. > > >>> I can not reproduce this error. > > >>> > > >> I am compiling on Intel XEON server with ubuntu 18.04 > > > Any update?? > > The uadk lib needs cross-compile on x86. > > Toolchain: > > https://urldefense.proofpoint.com/v2/url?u=https- > > 3A__releases.linaro.org_components_toolchain_binaries_latest- > 2D7_aarch64- > > 2Dlinux- > > > 2Dgnu_&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=DnL7Si2wl_PRwpZ9TWey > > > 3eu68gBzn7DkPwuqhd6WNyo&m=91MX2Cs8jDO3kZ8m02cjnNdNxbSoW7V9DE > > o6KPhTRzdWILxa_DQzYPoa5c5Lq9Q8&s=2- > > jhckUNn9LCXbLaFaAEdl_5seC82SCXxvkVQEPnNz0&e= > > Details are documented in https://urldefense.proofpoint.com/v2/url?u=https- > > > 3A__github.com_Linaro_uadk_blob_master_INSTALL&d=DwIDaQ&c=nKjWec2b > > > 6R0mOyPaz7xtfQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m > > > =91MX2Cs8jDO3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9 > > Q8&s=pyjDRDPApEQXxPjZ4q0QlXT5DgmAAYdZtNscFbRp8lk&e= > > > > Considering the confusion caused by simple build info in README, > > We are planning to remove the simple build step in README, only keeps > > INSTALL. > > https://urldefense.proofpoint.com/v2/url?u=https- > > > 3A__github.com_Linaro_uadk_pull_510&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7x > > > tfQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m=91MX2Cs8jD > > > O3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9Q8&s=m6I26 > > VelKVBjODnByclMKGtmaSEN2kv8ACeZsWbPTg4&e= > > > > Since there are some dependent libraries (libz & openssl) causes > > cross-compile complicated. > > We are planning to omit build tests if not found these libs > > https://urldefense.proofpoint.com/v2/url?u=https- > > > 3A__github.com_Linaro_uadk_pull_508&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7x > > > tfQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m=91MX2Cs8jD > > > O3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9Q8&s=tcbWSI > > hyL8b2mX4-Ta54bR4kH2fNkezlmVD24I09mTc&e= > > > > Only libnuma is must required for lib. > > Fortunately the numa cross compile is simple > > > > https://urldefense.proofpoint.com/v2/url?u=https- > > > 3A__github.com_Linaro_uadk_blob_master_INSTALL&d=DwIDaQ&c=nKjWec2b > > > 6R0mOyPaz7xtfQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m > > > =91MX2Cs8jDO3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9 > > Q8&s=pyjDRDPApEQXxPjZ4q0QlXT5DgmAAYdZtNscFbRp8lk&e= > > $git clone https://urldefense.proofpoint.com/v2/url?u=https- > > > 3A__github.com_numactl_numactl.git&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7xt > > > fQ&r=DnL7Si2wl_PRwpZ9TWey3eu68gBzn7DkPwuqhd6WNyo&m=91MX2Cs8jD > > > O3kZ8m02cjnNdNxbSoW7V9DEo6KPhTRzdWILxa_DQzYPoa5c5Lq9Q8&s=hZdhP > > WLMGMgV9tP7nEQY1G_iWnODYJMCfR41whWchSU&e= > > $cd numactl > > $./autogen.sh > > $autoconf -i > > $CC=aarch64-linux-gnu-gcc ./configure --host=i386-linux-gnu > > --target=aarch64-linux-gnu --prefix=${LIBROOT}/usr/local > > $make > > $make install > > > > Do you think we still need paste uadk build steps (and cross-compile steps) > > on dpdk doc/guides/cryptodevs/uadk.rst > > > Is it not possible to use pkg-config? > > Also while building on DPDK which config file is needed? > Do you need that also to be cross compiled? And even if I do manual copy of numa(lib and headers) in the toolchain (which I believe should not be done). I still see issues in installing uadk. It does not allow to install in a directory and does not make a pkgconfig file which can be used by DPDK to build the crypto driver. Please check how other PMDs are doing with external libs. In DPDK, we take external dependent libs via pkg-config only.