From owner-freebsd-hackers Thu May 9 6:10: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 3A0B837B408 for ; Thu, 9 May 2002 06:10:03 -0700 (PDT) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.11.6/8.10.2) with ESMTP id g49D9vv26721 for ; Thu, 9 May 2002 13:09:57 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Thu, 9 May 2002 13:09:56 +0000 (GMT) From: "E.B. Dreger" To: hackers@freebsd.org Subject: per-user or -proc CPU reservation and limits Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greetings, How difficult would it be to implement per-user or -process CPU reservation, a la ALTQ or other bandwidth reservation? Although FreeBSD has a nice scheduler, it would be even nicer to reserve x% of CPU cycles for a certain user or process, to have CPU throttling, et cetera. IOW, split the scheduler into "subschedulers", then have rules to group processes into subschedulers based on . Suggestions? -- Eddy Brotsman & Dreger, Inc. - EverQuick Internet Division Phone: +1 (316) 794-8922 Wichita/(Inter)national Phone: +1 (785) 865-5885 Lawrence ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Date: Mon, 21 May 2001 11:23:58 +0000 (GMT) From: A Trap To: blacklist@brics.com Subject: Please ignore this portion of my mail signature. These last few lines are a trap for address-harvesting spambots. Do NOT send mail to , or you are likely to be blocked. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message