From owner-freebsd-hackers Thu Aug 17 8:53:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po9.andrew.cmu.edu (PO9.ANDREW.CMU.EDU [128.2.10.109]) by hub.freebsd.org (Postfix) with ESMTP id 4A72637B6F9 for ; Thu, 17 Aug 2000 08:53:31 -0700 (PDT) Received: (from postman@localhost) by po9.andrew.cmu.edu (8.9.3/8.9.3) id LAA12713; Thu, 17 Aug 2000 11:53:23 -0400 (EDT) Received: via switchmail; Thu, 17 Aug 2000 11:53:23 -0400 (EDT) Received: from unix8.andrew.cmu.edu via qmail ID ; Thu, 17 Aug 2000 11:52:39 -0400 (EDT) Received: from unix8.andrew.cmu.edu via qmail ID ; Thu, 17 Aug 2000 11:52:39 -0400 (EDT) Received: from mms.4.60.May..8.2000.10.35.10.sun4.57.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix8.andrew.cmu.edu.sun4x.57 via MS.5.6.unix8.andrew.cmu.edu.sun4_57; Thu, 17 Aug 2000 11:52:39 -0400 (EDT) Message-ID: Date: Thu, 17 Aug 2000 11:52:39 -0400 (EDT) From: Thomas Valentino Crimi To: hackers@freebsd.org, Karl Pielorz Subject: Re: Critical (or equivalent) section in Userland? Cc: In-Reply-To: <399BA212.A84240AE@tdx.co.uk> References: <399BA212.A84240AE@tdx.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Excerpts from FreeBSD-Hackers: 17-Aug-100 Critical (or equivalent) se.. by Karl Pielorz@tdx.co.uk > The software is running as user 'root' - does anyone have any pointers on how > I can do this? (or how close I'll be able to get to doing this) - Theres only > going to be around 6 or 7 calls to rename() but I must ensure they _all_ > happen before any other process is allowed to run again... Take a look at rtprio(2), giving yourself a realtime priority will guarantee you the CPU until you explicitly release it (or another higher priority realtime process comes along). I'm not sure if the same deadlock potential that exists with giving a process an idle priority exists due to locking in the kernel, although I see no mention of it in the man pages. It's definitely something I'd be wary of, though. Regards, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message