All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iratxo Pichel Ortiz <ipichel@albentia.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	"Noelia Morón" <nmoron@albentia.com>,
	"'Rodrigo Partearroyo'" <rpartearroyo@albentia.com>
Subject: Re: NOHZ: local_softirq_pending
Date: Thu, 18 Jun 2009 18:52:09 +0200	[thread overview]
Message-ID: <4A3A70B9.4070702@albentia.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0906181048500.2800@localhost.localdomain>

Thomas,

Thomas Gleixner wrote:
> No, what happens is that the -RT starvation protector kicks in. That's
> a mechanism which checks whether the CPU is monopolized by rt tasks
> for longer than 950ms. It then blocks execution of rt tasks for
> 50ms. The silly thing is that it goes idle, but that's a different
> problem.
>   
> It's default on and can be disabled via:
>
> echo 0 > /proc/sys/kernel/rt_runtime_us
>
> Sorry that I did not notice that earlier, but when that triggers, then
> something is really wrong. There should never be a situation where -rt
> tasks (neither irq threads nor softirqs) should monopolize the CPU.
>   
No problem at all! Please let me know if the following assumption is 
right: This protection mechanism is dependent on the available CPU 
power. I mean, if the system has low CPU power, and if, for example, the 
network has very very high load, the total time taken to process all the 
data will be long. Generally much longer than in more powerful systems, 
so this protection arises. Is this right or it should not happen by 
design of the softirqs/RT tasks?

Anyway, seems to be correctly working. I still have to check why with  
HZ=100 it was periodically happening this events even with low load, but 
that could be very probably related to my software.

Again, thank you very much.

Best regards,

    Iratxo.
> Thanks,
>
> 	tglx
>
>   


-- 
Iratxo Pichel Ortiz
Software Development Manager

Albentia Systems S.A.
http://www.albentia.com

Tel: +34 914400567
Cel: +34 663808405
Fax: +34 914400569

C\Margarita Salas 22
Parque Tecnológico de Leganés
Leganés (28918)
Madrid
Spain


--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-06-18 16:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 15:28 NOHZ: local_softirq_pending Iratxo Pichel Ortiz
2009-06-14 19:50 ` Iratxo Pichel Ortiz
2009-06-15 13:19   ` Thomas Gleixner
2009-06-15 14:38     ` Iratxo Pichel Ortiz
     [not found]       ` <8e6b7a710906160101x6a8ae9d5qa7638627f513278@mail.gmail.com>
2009-06-16  8:26         ` NOHZ: local_softirq_pending - More info without need for specific code Iratxo Pichel Ortiz
     [not found]         ` <4A376450.5020209@albentia.com>
2009-06-16  9:26           ` Iratxo Pichel Ortiz
2009-06-16 14:45             ` NOHZ: local_softirq_pending Iratxo Pichel Ortiz
2009-06-16 18:39               ` Iratxo Pichel Ortiz
2009-06-17 22:03                 ` Thomas Gleixner
2009-06-17 22:35                   ` Iratxo Pichel Ortiz
2009-06-17 23:46                     ` Thomas Gleixner
2009-06-18  0:33                       ` Iratxo Pichel Ortiz
2009-06-18  8:57                         ` Thomas Gleixner
2009-06-18 16:52                           ` Iratxo Pichel Ortiz [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=4A3A70B9.4070702@albentia.com \
    --to=ipichel@albentia.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nmoron@albentia.com \
    --cc=rpartearroyo@albentia.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.