[dpdk-dev] [PATCH v8 01/25] eal: define macro container_of
Shreyansh Jain
shreyansh.jain at nxp.com
Wed Aug 31 06:26:14 CEST 2016
Hi Thomas,
On Tuesday 30 August 2016 07:12 PM, Thomas Monjalon wrote:
> 2016-08-30 17:29, Shreyansh Jain:
>> On Tuesday 30 August 2016 04:00 PM, Thomas Monjalon wrote:
>>> 2016-08-30 09:57, Shreyansh Jain:
>>>> Is there a better way to test that no driver breaks? Any particular
>>>> parameters I should use for test-build.sh?
>>>
>>> Yes I suggest to create a file ~/.config/dpdk/devel.config to adapt the
>>> configuration to your system.
>>> Once you have installed the required dependencies, you can make this kind
>>> of configuration:
>>
>> Ok.
>>
>>> mlxdep=$root/mlx/mofed-3.3-1.0.0.0
>>> szedep=$root/sze/usr-1.1.4
>>
>> What does '$root' here refer to?
>
> It is the directory where I compile the DPDK dependencies.
Ok - understood. I guessed the same
>
>> I am assuming 'mofed-3.3-1.0.0.0' and 'usr-1.1.4' are part of some
>> dependencies that I should be revolving. Is that so?
>
> Yes, download and compile them as explain in the respective guides.
Ok.
>
>> As of now I don't have much idea about this - I will have a look and
>> ping back in case I am stuck.
>>
>>> if echo $DPDK_TARGET | grep -q '^x86_64' ; then
>>> export DPDK_DEP_ARCHIVE=y
>>> export DPDK_DEP_ZLIB=y
>>> export DPDK_DEP_PCAP=y
>>> export DPDK_DEP_SSL=y
>
> You need to install the packages to resolve these dependencies
> (libarchive-dev, libzip-dev, libpcap-dev, libcrypto-dev).
Thanks for the info.
>
>>> export DPDK_DEP_MOFED=y
>>> export DPDK_DEP_SZE=y
>>> export DPDK_DEP_CFLAGS="-I$mlxdep/include -I$szedep/include"
>>> export DPDK_DEP_LDFLAGS="-L$mlxdep/lib -L$szedep/lib64 -rpath=$szedep/lib64"
>>> export AESNI_MULTI_BUFFER_LIB_PATH=$root/aesni/ipsec-043
>>> export LIBSSO_SNOW3G_PATH=$root/libsso/libsso-snow3g-0.3.1
>>> export LIBSSO_KASUMI_PATH=$root/libsso/libsso-kasumi-0.3.1
>>> fi
>>
>> Thanks. I will try the above.
>>
>>>
>>>> I used 'x86_64-native-linuxapp-gcc+default+debug+shared' for all patches.
>>>
>>> It is a good idea to test also with clang (x86_64-native-linuxapp-clang)
>>> and another arch (e.g. arm64-thunderx-linuxapp-gcc).
>>
>> Before releasing v9, I will do these steps.
>> Thank you for suggestions.
>
>
-
Shreyansh
More information about the dev
mailing list