netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: jamal <hadi@cyberus.ca>, "David S. Miller" <davem@davemloft.net>,
	Matheos.Worku@Sun.COM, jesse.brandeburg@intel.com,
	jarkao2@gmail.com, netdev@vger.kernel.org
Subject: Re: 2.6.24 BUG: soft lockup - CPU#X
Date: Fri, 28 Mar 2008 15:12:48 +0100	[thread overview]
Message-ID: <20080328141246.GD29218@elte.hu> (raw)
In-Reply-To: <20080328132643.GA24180@gondor.apana.org.au>


* Herbert Xu <herbert@gondor.apana.org.au> wrote:

> I agree that using jiffies is a pretty coarse approximation of proper 
> scheduling.  However, in the absence of a better solution we have to 
> live with it.
> 
> Perhaps running these out of process context is the correct approach.

yes. Such anonymous work loops inside softirq context are a disaster to 
TCP determinism and a disaster to scheduling in general (the wrong guy 
gets credited with the overhead). Softirqs were a neat hack 10 years 
ago, now if we know the target task for some workload we should execute 
as much of the workload in that task's context as possible. (and even 
for stuff where we dont have a 'target task' - routing, filtering, etc. 
- it might be better to use kernel threads.)

	Ingo

  parent reply	other threads:[~2008-03-28 14:13 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 16:46 2.6.24 BUG: soft lockup - CPU#X Matheos Worku
2008-03-26 17:31 ` Rick Jones
2008-03-26 20:14 ` Jarek Poplawski
2008-03-26 20:26   ` Matheos Worku
2008-03-26 21:46     ` Jarek Poplawski
2008-03-26 21:53       ` Jarek Poplawski
2008-03-27 10:33     ` Jarek Poplawski
2008-03-27 23:18       ` Brandeburg, Jesse
2008-03-27 23:45         ` Matheos Worku
2008-03-28  0:02           ` David Miller
2008-03-28  0:19             ` Matheos Worku
2008-03-28  0:34               ` David Miller
2008-03-28  1:22                 ` Herbert Xu
2008-03-28  1:38                   ` David Miller
2008-03-28 10:29                     ` Herbert Xu
2008-03-28 10:56                       ` Ingo Molnar
2008-03-28 11:06                         ` Herbert Xu
2008-03-28 11:29                           ` Herbert Xu
2008-03-28 12:19                             ` jamal
2008-03-28 13:26                               ` Herbert Xu
2008-03-28 14:07                                 ` jamal
2008-03-28 14:12                                 ` Ingo Molnar [this message]
2008-03-28 23:25                             ` David Miller
2008-03-28 14:09                           ` Ingo Molnar
2008-03-28  1:58                   ` Matheos Worku
2008-03-28 10:33                     ` jamal
2008-03-28 17:00                       ` Matheos Worku
2008-03-28 10:38                     ` Herbert Xu
2008-03-28 13:38                       ` Jarek Poplawski
2008-03-28 13:53                         ` Herbert Xu
2008-03-28 14:39                           ` Jarek Poplawski
2008-03-28 14:56                             ` Herbert Xu
2008-03-28 15:29                               ` Jarek Poplawski
2008-03-28 15:47                                 ` Jarek Poplawski
2008-03-29  1:06                                 ` Herbert Xu
2008-03-29  9:11                                   ` Jarek Poplawski

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=20080328141246.GD29218@elte.hu \
    --to=mingo@elte.hu \
    --cc=Matheos.Worku@Sun.COM \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=herbert@gondor.apana.org.au \
    --cc=jarkao2@gmail.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.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).