From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: peterz@infradead.org, davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: regression with napi/softirq ?
Date: Wed, 17 Jul 2019 21:19:25 +0100 [thread overview]
Message-ID: <20190717201925.fur57qfs2x3ha6aq@debian> (raw)
Hi All,
I am using v4.14.55 on an Intel Atom based board and I am seeing network
packet drops frequently on wireshark logs. After lots of debugging it
seems that when this happens softirq is taking huge time to start after
it has been raised. This is a small snippet from ftrace:
<...>-2110 [001] dNH1 466.634916: irq_handler_entry: irq=126 name=eth0-TxRx-0
<...>-2110 [001] dNH1 466.634917: softirq_raise: vec=3 [action=NET_RX]
<...>-2110 [001] dNH1 466.634918: irq_handler_exit: irq=126 ret=handled
ksoftirqd/1-15 [001] ..s. 466.635826: softirq_entry: vec=3 [action=NET_RX]
ksoftirqd/1-15 [001] ..s. 466.635852: softirq_exit: vec=3 [action=NET_RX]
ksoftirqd/1-15 [001] d.H. 466.635856: irq_handler_entry: irq=126 name=eth0-TxRx-0
ksoftirqd/1-15 [001] d.H. 466.635857: softirq_raise: vec=3 [action=NET_RX]
ksoftirqd/1-15 [001] d.H. 466.635858: irq_handler_exit: irq=126 ret=handled
ksoftirqd/1-15 [001] ..s. 466.635860: softirq_entry: vec=3 [action=NET_RX]
ksoftirqd/1-15 [001] ..s. 466.635863: softirq_exit: vec=3 [action=NET_RX]
So, softirq was raised at 466.634917 but it started at 466.635826 almost
909 usec after it was raised.
If I move back to v4.4 kernel I still see similar behaviour but the maximum
delay I get is in the range of 500usec. But if I move back to v3.8 kernel I
can see there is no packet loss and the maximum delay between softirq_raise
and irq_handler_entry is 103usec.
Is this a known issue?
Will really appreciate your help in this problem.
--
Regards
Sudip
next reply other threads:[~2019-07-17 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 20:19 Sudip Mukherjee [this message]
2019-07-17 20:53 ` regression with napi/softirq ? Thomas Gleixner
2019-07-17 21:40 ` Sudip Mukherjee
2019-07-17 21:52 ` Thomas Gleixner
2019-07-18 6:58 ` Eric Dumazet
2019-07-18 11:18 ` Sudip Mukherjee
2019-07-18 11:42 ` Eric Dumazet
2019-07-18 12:55 ` Sudip Mukherjee
2019-07-18 15:08 ` Eric Dumazet
2019-07-19 15:53 ` Sudip Mukherjee
2019-07-18 12:40 ` Thomas Gleixner
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=20190717201925.fur57qfs2x3ha6aq@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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