[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTiknwh4N3xRFQXYq0AFPc5BxWwUkuA@mail.gmail.com>
Date: Tue, 7 Jun 2011 11:57:24 -0300
From: Lucas De Marchi <lucas.de.marchi@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Remy Bohmer <linux@...mer.net>,
Armin Steinhoff <armin@...inhoff.de>,
Thomas Gleixner <tglx@...utronix.de>,
Johannes Bauer <hannes_bauer@....at>,
Monica Puig-Pey <puigpeym@...can.es>,
Rolando Martins <rolando.martins@...il.com>,
linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Changing Kernel thread priorities
On Tue, Jun 7, 2011 at 11:14, Peter Zijlstra <peterz@...radead.org> wrote:
> > Well, I 100% agree that it must be under full userspace control to be
> > able to set the priorities. But, the kernel default assumption of
> > starting everything at 50 is wrong as well.
> > Imagine the following situation:
> > * Realtime application is running and has threads active in the range
> > of prios 20 - 90.
> > * Now bring up a network device, it immediately starts spamming the
> > system at prio 50 _before_ you have the chance to set it below 20 by
> > means of chrt.
> > * RT behaviour is gone!
Why is the application using priorities in the range 20-90 if it's
well known that we default RT kernel threads to 50?
IMO it's a mistake in the application.
Lucas De Marchi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists