From: Eric Dumazet <eric.dumazet@gmail.com>
To: soukjin.bae@samsung.com,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [Kernel][NET] Bug report on packet defragmenting
Date: Wed, 7 Nov 2018 17:43:09 -0800 [thread overview]
Message-ID: <91b43bec-cb19-b94b-8ee3-26979e3a19d1@gmail.com> (raw)
In-Reply-To: <20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p4>
On 11/07/2018 05:29 PM, 배석진 wrote:
> If ipv6_defrag hook is not excuted simultaneously, then it's ok.
> ipv6_defrag hook can handle that. [exam 3]
This seems wrong.
This is the root cause, we should not try to work around it but fix it.
There is no guarantee that RSS/RPS/RFS can help here, packets can sit in per-cpu
backlogs long enough to reproduce the issue, if RX queues interrupts are spread
over many cpus.
next prev parent reply other threads:[~2018-11-08 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p4>
2018-11-08 1:29 ` [Kernel][NET] Bug report on packet defragmenting 배석진
2018-11-08 1:43 ` Eric Dumazet [this message]
[not found] ` <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p5>
2018-11-08 2:05 ` 배석진
2018-11-08 3:24 ` (2) " Eric Dumazet
2018-11-08 3:56 ` Eric Dumazet
[not found] ` <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p6>
2018-11-08 4:10 ` 배석진
2018-11-08 4:26 ` (2) " Eric Dumazet
2018-11-08 6:13 ` Eric Dumazet
[not found] ` <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p2>
2018-11-08 7:58 ` 배석진
2018-11-08 15:12 ` (2) " Eric Dumazet
[not found] ` <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p1>
2018-11-09 0:42 ` 배석진
2018-11-09 1:58 ` (2) " Eric Dumazet
2018-11-09 2:24 ` 배석진
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=91b43bec-cb19-b94b-8ee3-26979e3a19d1@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=soukjin.bae@samsung.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).