From: Jeff Weeks <jweeks@neuraldk.org>
To: dev@dpdk.org
Subject: [dpdk-dev] traffic no longer readable...
Date: Wed, 20 May 2015 11:11:50 -0400 [thread overview]
Message-ID: <4184471.eVetuCRXHp@neuralfour> (raw)
Hello all,
I've been developing with dpdk, using virtio, and I'm noticing that I can
often get into a state whereby I no longer receive any packets.
The call to rte_eth_rx_burst always returns 0, indicating the rx queue is
empty.
How is this queue filled? I see there is a dpdk thread, which waits on an
epoll fd for interrupts. I set a breakpoint here, and it appeared as though
we were waiting forever on the epoll fd. This, to me, seemed to be the source
of the issue I'm seeing (presumably interrupts cause us to read off the nic and
fill the queue?)... but, oddly enough, I see the same behaviour even when I'm
receiving packets.
Have I misinterpreted how this is supposed to work? Or is gdb behaving poorly
for me (wouldn't be surprising...).
What/how else can I further investigate this?
Thanks,
Jeff
next reply other threads:[~2015-05-20 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 15:11 Jeff Weeks [this message]
2015-05-20 15:33 ` Thomas Monjalon
2015-05-20 15:59 [dpdk-dev] Fwd: " Jeff Weeks
2015-05-20 16:31 ` [dpdk-dev] " Thomas Monjalon
2015-05-21 18:33 ` Jeff Weeks
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=4184471.eVetuCRXHp@neuralfour \
--to=jweeks@neuraldk.org \
--cc=dev@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).