Date: Fri, 19 Mar 2004 02:51:50 +0100
From: Diego Calleja =?ISO-8859-15?Q?Garc=EDa?= <diegocg@teleline.es>
To: Bill Davidsen <davidsen@tmr.com>
Cc: riel@redhat.com, andrea@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc1-aa1
Message-Id: <20040319025150.7a45f8a9.diegocg@teleline.es>
In-Reply-To: <405A4015.40108@tmr.com>
References: <Pine.LNX.4.44.0403181144290.16728-100000@chimarrao.boston.redhat.com>
	<20040318211532.293bb63c.diegocg@teleline.es>
	<405A4015.40108@tmr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1149
Lines: 23

El Thu, 18 Mar 2004 19:34:29 -0500 Bill Davidsen <davidsen@tmr.com> escribi?:

> Have a bit of caution there, cdrecord sets itself realtime priority, 
> locks pages in memory, and ensures that the process is likely to work 
> even under load. I don't think addressing just a part of the problem 
> will result in reliability under load. You would have to look at 
> capabilities to allow these things to be done, under load they may not 
> keep up depending on what's going on. Good to get a start, don't assume 
> all the issues are addressed.


Yes, the following message is:
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.

But since 2.6 uses DMA for recording the CPU usage is really low...I guess
people will still use suid for that :)
-
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/