> -邮件原件-
> 发件人: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> 发送时间: 2020年5月14日 9:22
> 收件人: Lilijun (Jerry) ; 'dev@dpdk.org'
>
> 抄送: wangyunjian ; xudingke
> ; 'sta...@dpdk.org' ; nd
> ; yipeng1.w...@intel.com; Honnappa Nagaraha
> -邮件原件-
> 发件人: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> 发送时间: 2020年5月14日 3:27
> 收件人: Lilijun (Jerry) ; 'dev@dpdk.org'
>
> 抄送: wangyunjian ; xudingke
> ; 'sta...@dpdk.org' ; nd
> ; yipeng1.w...@intel.com; nd ; Honnappa
>
> -邮件原件-
> 发件人: Wang, Yipeng1 [mailto:yipeng1.w...@intel.com]
> 发送时间: 2020年5月13日 7:41
> 收件人: Lilijun (Jerry) ; Honnappa Nagarahalli
> ; 'dev@dpdk.org'
> 抄送: wangyunjian ; xudingke
> ; 'sta...@dpdk.org' ; nd
> ; nd
> 主题: RE: [dpdk-dev] [PAT
> -邮件原件-
> 发件人: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> 发送时间: 2020年5月6日 7:18
> 收件人: Lilijun (Jerry) ; 'dev@dpdk.org'
>
> 抄送: wangyunjian ; xudingke
> ; 'sta...@dpdk.org' ; nd
> ; Honnappa Nagarahalli ;
> yipeng1.w...@
all keys. Just some selected keys and
data are deleted and released.
Jerry.
-邮件原件-
发件人: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
发送时间: 2020年4月29日 4:46
收件人: Lilijun (Jerry) ; 'dev@dpdk.org'
抄送: wangyunjian ; xudingke ;
'sta...@dpdk.org' ; nd ; Honnap
>From 0faea722b82ffe30adfa55d5ea4ad3a23ed30d4e Mon Sep 17 00:00:00 2001
From: Yunjian Wang
Date: Mon, 27 Apr 2020 11:12:25 +0800
Subject: [PATCH] lib/librte_hash: avoid iterate bugs with delete keys.
The keys idx are stored in rte_hash main and extend bucket key slots.
We iterate every no empty K
eate;
rte_hash_del_key;
+ rte_hash_del_key_fixed;
rte_hash_del_key_with_hash;
rte_hash_find_existing;
rte_hash_free;
--
2.19.1
-邮件原件-
发件人: Lilijun (Jerry)
发送时间: 2020年4月18日 18:00
收件人: 'dev@dpdk.org' ; 'sta...@dpdk.org'
主题: rte_hash bug: can&#x
ny ideas or solutions on this bug? Thanks.
Jerry.
ntly?
2) Can we support multithread writing with
RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF being set? Do we need add
RTE_HASH_EXTRA_FLAGS_MULTI_WRITER_ADD flag?
Any reply will be appreciated very much. Thanks.
Jerry
config: add emag configuration
mk/machine: add emag machine configurations
eMAG is Ampere Computing 64-bit ARM processor
with 32 Arm v8 64-bit CPU cores.
For more information, refer to:
https://amperecomputing.com/product/
Signed-off-by: Jerry Hao OS
---
config/arm/arm64_emag_linux_gcc
*** BLURB HERE ***
Jerry Hao OS (1):
build: add emag(arm64) platform and default config
config/arm/arm64_emag_linux_gcc | 15
config/arm/meson.build | 11 -
config/defconfig_arm64-emag-linux-gcc| 1 +
config/defconfig_arm64-emag-linuxapp
This patch is to add the emag default CACHE_LINE_SIZE
settings and ARCH variable definitions;
Added the meson build config.
Signed-off-by: Jerry Hao OS
---
config/arm/arm64_emag_linux_gcc | 15
config/arm/meson.build | 11 -
config/defconfig_arm64
This patch is to add the emag default CACHE_LINE_SIZE
settings and ARCH variable definitions
Signed-off-by: Jerry Hao OS
---
config/defconfig_arm64-emag-linux-gcc| 1 +
config/defconfig_arm64-emag-linuxapp-gcc | 8 ++
mk/machine/emag/rte.vars.mk | 31
*** BLURB HERE ***
Jerry Hao OS (1):
build: add emag(arm64) platform and default config
config/defconfig_arm64-emag-linux-gcc| 1 +
config/defconfig_arm64-emag-linuxapp-gcc | 8 ++
mk/machine/emag/rte.vars.mk | 31
3 files changed, 40 insertions
From: Jerry Hao
This patch is to add the emag default CACHE_LINE_SIZE
settings and ARCH variable definitions.
Signed-off-by: Jerry Hao OS
---
config/defconfig_arm64-emag-linux-gcc| 1 +
config/defconfig_arm64-emag-linuxapp-gcc | 8 ++
mk/machine/emag/rte.vars.mk | 31
*** BLURB HERE ***
Jerry Hao (1):
build: add emag(arm64) platform and default config
config/defconfig_arm64-emag-linux-gcc| 1 +
config/defconfig_arm64-emag-linuxapp-gcc | 8 ++
mk/machine/emag/rte.vars.mk | 31
3 files changed, 40 insertions
This patch is to add the emag default CACHE_LINE_SIZE
settings and ARCH variable definitions.
Signed-off-by: Jerry Hao
---
config/defconfig_arm64-emag-linux-gcc| 1 +
config/defconfig_arm64-emag-linuxapp-gcc | 8 ++
mk/machine/emag/rte.vars.mk | 31
*** BLURB HERE ***
Jerry Hao (1):
build: add emag(arm64) platform and default config
config/defconfig_arm64-emag-linux-gcc| 1 +
config/defconfig_arm64-emag-linuxapp-gcc | 8 ++
mk/machine/emag/rte.vars.mk | 31
3 files changed, 40 insertions
This patch is to add the emag default CACHE_LINE_SIZE settings and ARCH
variable definitions
Signed-off-by: Jerry Hao
---
config/defconfig_arm64-emag-linux-gcc| 1 +
config/defconfig_arm64-emag-linuxapp-gcc | 8 ++
mk/machine/emag/rte.vars.mk | 31
*** BLURB HERE ***
Jerry Hao (1):
build: add emag(arm64) platform and default configurations;
config/defconfig_arm64-emag-linux-gcc| 1 +
config/defconfig_arm64-emag-linuxapp-gcc | 8 ++
mk/machine/emag/rte.vars.mk | 31
3 files changed, 40
Hi Anatoly,
> -Original Message-
> From: Burakov, Anatoly [mailto:anatoly.bura...@intel.com]
> Sent: Friday, March 08, 2019 5:38 PM
> To: Lilijun (Jerry, Cloud Networking) ;
> dev@dpdk.org
> Cc: jerry.zh...@intel.com; ian.sto...@intel.com
> Subject: Re: [dpdk-de
> -Original Message-
> From: chasmosau...@gmail.com [mailto:chasmosau...@gmail.com] On
> Behalf Of Chas Williams
> Sent: Monday, September 17, 2018 12:02 AM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] bonding: add
Hi all,
Currently dpdk acl search can be done by calling rte_acl_classify(). In some
usecases, we need lookup the acl table again staring from a specific rule index.
Are there anyone do some research or has some opinions about this question?
Thanks.
B.R.
Jerry
Hi all,
In the function bond_mode_8023ad_enable(), the var i is to used to as the
second parameter to pass the slave dev's dpdk port id to the function
bond_mode_8023ad_activate_slave().
I think this variable is only a index for array internals->active_slaves. So
its need to be fixed and chang
MAX_LCORE=1024
>+CONFIG_RTE_MAX_NUMA_NODES=16
> CONFIG_RTE_MAX_MEMSEG=256
> CONFIG_RTE_MAX_MEMZONE=2560
> CONFIG_RTE_MAX_TAILQ=32
>--
Did you test it and make sure that there is no issue on 16 node servers?
BRs,
Jerry
Hi,
Please provide the environment info such as kernel version, DPDK version and
the reproduce steps in detail.
Thanks!
>-Original Message-
>From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of zhangsha (A)
>Sent: Friday, January 30, 2015 7:40 PM
>To: dev at dpdk.org
>Subject:
t; EAL: PCI device :02:10.0 on NUMA socket -1
> EAL: probe driver: 8086:10ed rte_ixgbevf_pmd
> EAL: PCI memory mapped at 0x7f78b181f000
> EAL: PCI memory mapped at 0x7f78b181b000
> EAL: Error - exiting with code: 1
> Cause: Requested device :02:10.0 cannot be used
>
> Any suggestions?
>
> Thanks,
> Jerry
>
Met the similar issue before.
VT-d enabled? If so you may need to contact HP to upgrade the BIOS or you may
disable VT-d and remove iommu=pt intel_iommu=on if you don't need VF function.
>-Original Message-
>From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Hiroshi Shimamoto
>Sent:
Hi all,
Do you know why DPDK(shared library) constructor function
rte_cpu_check_supported() needs to check some unnecessary CPU flags which is
not used by current DPDK such as "AES"?
On Hehalem platform with GCC4.8, using shard DPDK library, it will report
AES is not supported. Bu
definition of ?machine_to_phys? was here
/usr/src/linux-3.0.76-0.11/arch/x86/include/asm/xen/page.h:159: error:
conflicting types for ?mfn_to_local_pfn?
/usr/src/linux-3.0.76-0.11/arch/x86/include/mach-xen/asm/maddr.h:96: error:
previous definition of ?mfn_to_local_pfn? was here
B.R.
Jerry
Hi,
On 2014/9/14 19:12, Zhang, Jerry wrote:
> Hi,
>
>> -Original Message-
>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of jerry
>> Sent: Sunday, September 14, 2014 5:01 PM
>> To: dev at dpdk.org
>> Cc: luonengjun at huawei.com
>> Su
parameters
Anyone know the issue and the corresponding fix? Thanks.
B.R.
Jerry
Hi,
>-Original Message-
>From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of jerry
>Sent: Sunday, September 14, 2014 5:01 PM
>To: dev at dpdk.org
>Cc: luonengjun at huawei.com
>Subject: [dpdk-dev] l2fwd mmap memory failed
>
>Hi all,
>
>The l2fwd sample a
>-Original Message-
>From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of rong wen
>Sent: Saturday, September 6, 2014 8:07 PM
>To: dev
>Subject: [dpdk-dev] dpdk 1.6 insmod rte_kni.ko error
>
>Hi All,
>
>I am a new guy to use dpdk. The kernel version is 2.6.32.
>
>After I build the rte_kn
>-Original Message-
>From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Anand S Angadi
>Sent: Monday, September 1, 2014 5:27 PM
>To: Matthew Hall
>Cc: dev at dpdk.org
>Subject: Re: [dpdk-dev] reg : adding grub entry with hugepages.
>
>On 09/01/2014 02:36 PM, Matthew Hall wrote:
>> On M
>> Hello everyone,
>> I am using fedora 16, i want to Add additional Grub entry with hugepages
>enabled permanently can u tell me how can i add?
>> and wher can i add?
>>
>> --
>> Thanks & Regards,
>> ANAND
>>
>>
>>
>>
>Hi Zhang,
>Thank you for your reply, now I am using same thing but i want it pe
Hi,
Here is an example to enable both 1G and 2M in kernel parameters.
default_hugepagesz=1G hugepagesz=1G hugepages=8 hugepagesz=2M hugepages=512
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Anand S Angadi
Sent: Monday, September 1, 2014 4:44 PM
To: dev at d
Hi,
'memzone already exists' is not an error for the
secondary DPDK process.
DPDK EAL initialization creates a mempool for log history. This mempool
creation includes creating a ring based on the memzone named RG_MP_log_history.
For the secondary DPDK process, if the mempool for l
Hi,
Make sure to add iommu=pt inte_iommu=on to kernel parameters if VT-d is
enabled.
Otherwise, the PF may not work well with igb_uio because of DMAR.
Please also refer to the comments in the DPDK getting started guide.
In addition, to run the Intel? DPDK with Intel? VT-d, the iommu=pt kernel
39 matches
Mail list logo
