Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <40CCFF18.C6CEFBAA@dessent.net> Date: Sun, 13 Jun 2004 18:27:52 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 CC: cygwin AT cygwin DOT com Subject: Re: nice not setting above/below normal References: <1981E79C7C98A547B36D794FBEC5337002967DF6 AT MOSCNTX1> <40C9A8BE DOT DF5B7EAF AT dessent DOT net> <20040613230958 DOT GA4084 AT efn DOT org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Yitzchak Scott-Thoennes wrote: > > On Fri, Jun 11, 2004 at 05:42:38AM -0700, Brian Dessent wrote: > > reserved for real-time processes. The remaining range 1-15 are the > > regular (dynamic) priorities that most processes run with. In reality > > you don't set the priority directly this way, rather you choose a > > priority class (realtime, high, normal, idle; corresponding to 24, 13, > > 8, 4) and then a modifier (highest, above normal, normal, below normal, > > lowest; corresponding to +2, +1, 0, -1, -2). > > Is that correct? Shouldn't idle be 3 to allow the full 1-15 range? According to sysinternals' Process Explorer, idle is indeed 4. I haven't double checked with anything on MSDN but I don't see why it would not be displaying the correct thing, given that it shows the priority on the 0-31 scale for every process so it must be using the NTDLL level calls. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/