Hello,
This is our proposal to introduce new PMD APIs, it would be much better to
integrate DPDK into various applications.
There is a gap in hardware offload when you porting DPDK to new platform which
support some offload features, like packet accelerator, buffer management etc.
If we can mak
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Wednesday, May 13, 2015 8:08 PM
> To: Mcnamara, John
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 0/2] doc: refactored fig and table nums
> into references
>
>
> The error is removed so
Hi Keith,
On 05/13/2015 04:43 PM, Wiles, Keith wrote:
>
>
> On 5/13/15, 9:28 AM, "Olivier MATZ" wrote:
>
>>
>> On 05/13/2015 04:04 PM, Wiles, Keith wrote:
>>>
>>>
>>> On 5/13/15, 8:56 AM, "Olivier MATZ" wrote:
>>>
Hi Keith,
On 05/13/2015 03:17 PM, Wiles, Keith wrote:
>>>
>>
Hi,
On 05/13/2015 06:35 PM, Keith Wiles wrote:
> Simplify the ifdefs in rte.app.mk to make the code more
> readable and maintainable by introducing a internal
> _LDLIBS-y variable to build up the LDLIBS variable.
>
> The new internal variable _LDLIBS-y should not be
> used outside of the rte.app.
Thank You Xie for reply,
When I run vhost with -m 2048 it didn't start, with -m 3000 and host with
1024 give me segfault (I calculated hugepages and have only 3 free)
VHOST_CONFIG: bind to usvhost
VHOST_CONFIG: new virtio connection is 26
VHOST_CONFIG: new device, handle is 0
VHOST_CONFIG: new vi
Simplify the ifdefs in rte.app.mk to make the code more
readable and maintainable by introducing a internal
_LDLIBS-y variable to build up the LDLIBS variable.
The new internal variable _LDLIBS-y should not be
used outside of the rte.app.mk file.
Signed-off-by: Keith Wiles
---
mk/rte.app.mk | 2
Signed-off-by: Keith Wiles
---
doc/build-sdk-quick.txt | 1 +
doc/guides/prog_guide/dev_kit_build_system.rst | 2 ++
doc/guides/prog_guide/dev_kit_root_make_help.rst | 2 +-
mk/rte.app.mk| 2 +-
4 files changed, 5 insertions(+), 2 del
On 5/14/15, 7:30 AM, "Olivier MATZ" wrote:
>Hi,
>
>On 05/13/2015 06:35 PM, Keith Wiles wrote:
>> Simplify the ifdefs in rte.app.mk to make the code more
>> readable and maintainable by introducing a internal
>> _LDLIBS-y variable to build up the LDLIBS variable.
>>
>> The new internal variable
Hi Keith,
On 05/14/2015 04:21 PM, Keith Wiles wrote:
> Simplify the ifdefs in rte.app.mk to make the code more
> readable and maintainable by introducing a internal
> _LDLIBS-y variable to build up the LDLIBS variable.
>
> The new internal variable _LDLIBS-y should not be
> used outside of the rt
Hi Helin,
Any news regarding this issue? do u know if there is any related patch I can
apply on my application in order to work with multi-segment packets?
Thanks,
Nissim
-Original Message-
From: Zhang, Helin [mailto:helin.zh...@intel.com]
Sent: Tuesday, May 12, 2015 11:51 AM
To: Nissi
At Tuesday's Beyond DPDK 2.0 call, one topic we discussed was decision making
and whether we need a Technical Steering Committee (TSC). As a follow-up to
that discussion, I'd like to propose that we create a TSC for DPDK to guide the
long-term strategic direction of the project.
Justification
Hello,
My Hardware consists of the following:
- DL380 Gen 9 Server supporting two Haswell Processors (Xeon CPU E5-2680 v3 @
2.50GHz)
- An x540 Ethernet Controller Card supporting 2x10G ports.
Software:
- CentOS 7 (3.10.0-229.1.2.el7.x86_64)
- DPDK 1.8
I want all the network traffic rece
2015-05-14 17:42, Olivier MATZ:
> Hi Keith,
>
> On 05/14/2015 04:21 PM, Keith Wiles wrote:
> > Simplify the ifdefs in rte.app.mk to make the code more
> > readable and maintainable by introducing a internal
> > _LDLIBS-y variable to build up the LDLIBS variable.
> >
> > The new internal variable
On Thu, 14 May 2015 21:38:24 +
"Assaad, Sami (Sami)" wrote:
> Hello,
>
> My Hardware consists of the following:
> - DL380 Gen 9 Server supporting two Haswell Processors (Xeon CPU E5-2680 v3
> @ 2.50GHz)
> - An x540 Ethernet Controller Card supporting 2x10G ports.
>
> Software:
> - Ce
Hi, there,
I recently noticed that sometimes packets are matched with the wrong ACL
rules when using the DPDK ACL library.
I tested it with the "testacl" under dpdk/build/app:
Here are my rule file and trace file:
cat test_data/rule1
@192.168.0.0/24 192.168.0.0/24 400 : 500 0 : 52 6/0xff
@192.168
15 matches
Mail list logo