From owner-soc-status@FreeBSD.ORG Mon Jul 2 20:29:08 2012 Return-Path: Delivered-To: soc-status@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AC351065674 for ; Mon, 2 Jul 2012 20:29:08 +0000 (UTC) (envelope-from rudotx@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3438F8FC0C for ; Mon, 2 Jul 2012 20:29:08 +0000 (UTC) Received: by werp13 with SMTP id p13so1139877wer.13 for ; Mon, 02 Jul 2012 13:29:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=0KaGjVKyBuHrpSWQTH84ZbXpt9TsQWV21GKhOC/rfGI=; b=y+Dfyn23DVa7dugXF8cVDbX2vxfrwGekNS9jG0vy06hzkGG8melONf7U+iT9607wJR m4j6xG6o9l39nnASnwOyq0KzgkdS900nN3XDFYMjxqwsqD+3nAXFTV0L1H8sRx2YstP3 G8Aq+LSV2d5aM8GHdCplu3YXGm39XikaZrBLh4zGV/0PKwAyoXtSQm/HsbQuGeNboOjU Lztt0Wi+3MSW8mSTGQDBhzPYsXr49WYqn/yPujQNpDOtIoUWzPGt7mMMucGOPjud1h8r bnRpxksrKIw2zQwRZOqiEStHlEjydisw4hW3LYEtZUPlYayqCupTn9OoJYkPaB4HNBkz R5NQ== Received: by 10.216.136.203 with SMTP id w53mr1613203wei.63.1341260947034; Mon, 02 Jul 2012 13:29:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.217.1.72 with HTTP; Mon, 2 Jul 2012 13:28:46 -0700 (PDT) From: rudo tomori Date: Mon, 2 Jul 2012 22:28:46 +0200 Message-ID: To: soc-status@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: cpu limits status report X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2012 20:29:08 -0000 Hi, the goal of my gsoc project is to enable the system administrators to configure %CPU limits using the rctl command. So that they can for example limit a particular user to 50% cpu time. Last week I wanted to run some benchmarks but in fact I spent it debugging the bugs I encountered during the benchmarking. First bug caused the freeze of my pc after about 2 hours of running make buildworld. I thought it was some kind of deadlock and it took me almost 3 days until I realised it was just a kernel panic. The kernel was configured to drop to the debugger on panic and because I was running X on this pc, I only observed freeze of the gui. After I realised it is kernel panic and got the panic message and backtrace, it wasn't too difficult to fix the problem. Then I encountered another bug that caused the make buildworld process hang. This problem was due to improper handling of zombie processes in my code. I think I have fixed it, but tested it only once - and it seems to be fixed. So the latest status of my project is this: I have been able to run make buildworld on behalf of a user that has limited %cpu availability. And it run without causing any panics or other problems. But I still need to test it more, possibly with different %cpu limits. Next week I will continue running benchmarks and I will debug the problems I will encounter. rudo