From: "shesha Sreenivasamurthy (shesha)" <shesha@cisco.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Packets not processed when huge pages are not used
Date: Wed, 21 Oct 2015 20:29:47 +0000 [thread overview]
Message-ID: <D24D43DC.23EFE%shesha@cisco.com> (raw)
Hi,
I have a packet processing application running correctly using hugepages with 82599 interface. However, when no-huge is set, I do not see any packets being processed by DPDK. When arp packets are sent to this interface, I see them being received by the device (BPRC counter gets incremented). However, the DD register does not get set by the hardware. Therefore, _recv_raw_pkts_vec() returns thinking that there are no packets (shown below). Therefore, when huge pages are not used, I suspect that some DMA configuration is getting messed up. Any tips on how to go about finding the issue will be helpful.
drivers/net/ixgbe/ixgbe_rxtx_vec.c
303 /* Before we start moving massive data around, check to see if
304 * there is actually a packet available */
305 if (!(rxdp->wb.upper.status_error &
306 rte_cpu_to_le_32(IXGBE_RXDADV_STAT_DD)))
307 return 0;
Observation: In lib/librte_eal/linuxapp/eal/eal_memory.c::rte_eal_hugepage_init() physical memory is set to be same as virtual (mcfg->memseg[0].phys_addr = (phys_addr_t)(uintptr_t)addr;). Is that expected ?
next reply other threads:[~2015-10-21 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 20:29 shesha Sreenivasamurthy (shesha) [this message]
2015-10-21 21:08 ` shesha Sreenivasamurthy (shesha)
2015-10-22 14:37 ` Sergio Gonzalez Monroy
2015-10-22 16:09 ` shesha Sreenivasamurthy (shesha)
2015-10-23 9:24 ` Sergio Gonzalez Monroy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D24D43DC.23EFE%shesha@cisco.com \
--to=shesha@cisco.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).