From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Wander Lairson Costa <wander@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
juri.lelli@redhat.com
Subject: Re: Splat in kernel RT while processing incoming network packets
Date: Wed, 9 Aug 2023 12:56:23 +0200 [thread overview]
Message-ID: <20230809105623.DSEPQ9LC@linutronix.de> (raw)
In-Reply-To: <6cmltsaeqjcekglutpnp4lxyqnjng5m4w73ae4btwrivuxvptf@zmhahab7643i>
On 2023-07-05 12:59:28 [-0300], Wander Lairson Costa wrote:
> Maybe, under RT, some softirq should run in the context of the "target"
> process. For NET_RX, for example, the softirq's would run in the context
> of the packet recipient process. Each task_struct would have a list of
> pending softirq, which would be checked in a few points, like on scheduling,
> when the process enters in the kernel, softirq raise, etc. The default
> target process would be ksoftirqd. Does this idea make sense?
We had something similar. The softirq runs in the context of the task
that raised it. So the networking driver raised NET_RX and it was
processed in its context (and still is). The only difference now is that
we no longer have a task based "raised bit" but a per-CPU.
For RPS you already pulled the skb from the NIC, you need to process it
and this isn't handled in the task's context but on a specific CPU.
Let me look at per-CPU backlog thread or ripping the warning out…
Sebastian
prev parent reply other threads:[~2023-08-09 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 12:47 Splat in kernel RT while processing incoming network packets Wander Lairson Costa
2023-07-03 13:20 ` Wander Lairson Costa
2023-07-03 14:29 ` Sebastian Andrzej Siewior
2023-07-03 21:15 ` Wander Lairson Costa
2023-07-04 10:05 ` Sebastian Andrzej Siewior
2023-07-04 10:29 ` Paolo Abeni
2023-07-04 14:47 ` Sebastian Andrzej Siewior
2023-07-05 15:59 ` Wander Lairson Costa
2023-08-09 10:56 ` Sebastian Andrzej Siewior [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=20230809105623.DSEPQ9LC@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wander@redhat.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).