Hi all,
Just to inform anyone who may be interested: but there will be an "Introduction
to DPDK" talk given by yours truly at OSCON in Portland next week:
http://www.oscon.com/oscon2014/public/schedule/detail/37678
All attendees welcome, and if any other DPDK developer folks are at the
confere
Keith,
I've observed same problem on our platforms. I'm using compiled kernel 3.14.11
on top of CentOS 6.5.
After modifying the value from 100 to 400 in Makefile for
max-inline-insns-single parameter, I am able to compile DPDK 1.7.0 successfully.
--anbu-
-Original Message-
From: dev [
2014-07-16 10:07, John W. Linville:
> On Tue, Jul 15, 2014 at 11:27:45PM +0200, Thomas Monjalon wrote:
> > 2014-07-14 09:46, John W. Linville:
> > > On Sat, Jul 12, 2014 at 12:34:46AM +0200, Thomas Monjalon wrote:
> > > > 2014-07-11 13:40, John W. Linville:
> > > > > Is there an example of code in
The CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG and CONFIG_RTE_LIBRTE_MBUF_DEBUG didn't
provide any input, so I also added the CONFIG_RTE_LIBRTE_ETHDEV_DEBUG and
CONFIG_RTE_LIBRTE_IGB_PMD.
below is a sample log showing the problem, though I don't see any clue in
the logs.
in this case pkt 58509 is placed at t
2.6.32 is minimum, but I believe still needs patches to fix hugetlbfs issues.
I think the first kernel which had all the features we need, and doesn't
require patches, is 2.6.33.6.
Jeff
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
Sent: Wednesday
2014-07-16 08:35, Neil Horman:
> On Tue, Jul 15, 2014 at 11:27:45PM +0200, Thomas Monjalon wrote:
> > 2014-07-14 09:46, John W. Linville:
> > > On Sat, Jul 12, 2014 at 12:34:46AM +0200, Thomas Monjalon wrote:
> > > > 2014-07-11 13:40, John W. Linville:
> > > > > Is there an example of code in DPDK
I will try it though I hope the amount of logs won't affect the result.
while analyzing the wireshark captures I noted that the packet i supposed
to capture arrives in a short time after the one before.
for example, here is a time between the consecutive transmitted packets:
0.5 PKT 12201
0
L3fwd-acl and ip pipeline apps were using old
x86_64-default-linuxapp-gcc as their default target,
instead of x86_64-native-linuxapp-gcc
Signed-off-by: Pablo de Lara
---
examples/ip_pipeline/Makefile |2 +-
examples/l3fwd-acl/Makefile |2 +-
2 files changed, 2 insertions(+), 2 deletion
Hi Konstantin,
On 07/15/2014 11:07 AM, Ananyev, Konstantin wrote:
>> As this change would impact the core of DPDK, I think it would be
>> interesting to list some representative use-cases in order to evaluate
>> the cost of each solution. This will also help for future modifications,
>> and could
Hello Helmut,
2014-07-16 13:56, Helmut Sim:
>> then i see that from time to time i get a packet that was already received
>> earlier instead of receiving the expected packet.
>> the output is:
>> PKT 12201
>> PKT 12202
>> PKT 12203
>> PKT 12204
>> PKT 12205
>> PKT 12206
>> PKT 12202
>> PKT 12208
>
Hi,
2014-07-16 13:56, Helmut Sim:
> then i see that from time to time i get a packet that was already received
> earlier instead of receiving the expected packet.
> the output is:
> PKT 12201
> PKT 12202
> PKT 12203
> PKT 12204
> PKT 12205
> PKT 12206
> PKT 12202
> PKT 12208
>
> total received pk
Hi,
I still can't get over this issue and need some help here.
in order to investigate this issue i wrote a very simple app that do:
rte_eth_rx_burst(port[i].portid, 0, pkts_burst, MAX_PKT_BURST)
printf the udp pkt content
rte_pktmbuf_free(pkts_burst[j]);
on my host i wro
On Tue, Jul 15, 2014 at 11:27:45PM +0200, Thomas Monjalon wrote:
> 2014-07-14 09:46, John W. Linville:
> > On Sat, Jul 12, 2014 at 12:34:46AM +0200, Thomas Monjalon wrote:
> > > 2014-07-11 13:40, John W. Linville:
> > > > Is there an example of code in DPDK that requires specific kernel
> > > > ver
On Tue, Jul 15, 2014 at 11:27:45PM +0200, Thomas Monjalon wrote:
> 2014-07-14 09:46, John W. Linville:
> > On Sat, Jul 12, 2014 at 12:34:46AM +0200, Thomas Monjalon wrote:
> > > 2014-07-11 13:40, John W. Linville:
> > > > Is there an example of code in DPDK that requires specific kernel
> > > > ver
> Thank you for the reply.
>
> By the way, I got an error message while compiling Open vSwitch. Is it
> essential to bind a port to igb_uio module in order to compile Open vSwitch
> without error? I just wonder whether the errors attached below just
> happened because I did not bind the port to th
Hi,
2014-07-14 14:17, Vijayakumar Muthuvel Manickam:
> *virtio_net_hdr_mem* member within *virtqueue* structure stores a
> physical address and is defined as void ptr. When 32bit pmd is used
> with 64bit kernel this leads to truncation of 64bit physical address
> and pkt i/o does not work.
> Chang
16 matches
Mail list logo
