Date: Thu, 24 Feb 2005 17:40:09 -0500
From: "Chad N. Tindel" <chad@tindel.net>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Helge Hafting <helge.hafting@aitel.hist.no>, Andrew Morton <akpm@osdl.org>,
       linux-kernel@vger.kernel.org
Subject: Re: Xterm Hangs - Possible scheduler defect?
Message-ID: <20050224224009.GA66192@calma.pair.com>
References: <20050223230639.GA33795@calma.pair.com> <20050223183634.31869fa6.akpm@osdl.org> <20050224052630.GA99960@calma.pair.com> <421DD5CC.5060106@aitel.hist.no> <20050224173356.GA11593@calma.pair.com> <16926.21614.267728.100131@wombat.chubb.wattle.id.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16926.21614.267728.100131@wombat.chubb.wattle.id.au>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 825
Lines: 20

> In many Unices, crucial kernel threads run at realtime priority with a
> static priority higher than is accessible to user code.

Yep.  

> That being said, however, you've got to be a privileged user to set
> real time very high priority on a thread, and if you do, you'd better
> know what you're doing.  Any SCHED_FIFO thread should run for a time,
> then sleep for a time, or it *will* DOS everything else on the
> processor.

This is only true if you're not doing what you said in your first paragraph,
i.e. running crucial kernel threads higher than any user thread.

Chad
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/