From: Joseph Vossen <jkvossen@vossen.org>
To: Jay Rolette <rolette@infiniteio.com>
Cc: DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] soft lockup calling receive burst
Date: Fri, 20 Mar 2015 15:04:10 -0400 [thread overview]
Message-ID: <BFEC750E-8CB4-43CF-B2CE-AF1A2C219091@vossen.org> (raw)
In-Reply-To: <CADNuJVp+O+Wt+epsJ3-Wjki2+E+Kx37Xb_e-K89uKxkCFNwDTA@mail.gmail.com>
[snip]
> I haven't seen that, but there's a soft-lockup in KNI in DPDK 1.6. Here's what I posted about that one a few weeks ago:
>
> Found the problem. No patch to submit since it's already fixed in later versions of DPDK, but thought I'd follow up with the details since I'm sure we aren't the only ones trying to use bleeding-edge versions of DPDK...
>
> In kni_net_rx_normal(), it was calling netif_receive_skb() instead of netif_rx(). The source for netif_receive_skb() point out that it should only be called from soft-irq context, which isn't the case for KNI.
>
> As typical, simple fix once you track it down.
>
> Yao-Po Wang's fix: commit 41a6ebded53982107c1adfc0652d6cc1375a7db9.
I noticed that posting, but KNI is not involved here...thanks!
prev parent reply other threads:[~2015-03-20 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 17:53 Joseph Vossen
2015-03-20 18:26 ` Jay Rolette
2015-03-20 19:04 ` Joseph Vossen [this message]
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=BFEC750E-8CB4-43CF-B2CE-AF1A2C219091@vossen.org \
--to=jkvossen@vossen.org \
--cc=bford@vossen.org \
--cc=dev@dpdk.org \
--cc=rolette@infiniteio.com \
/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).