From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 00DD4138825 for ; Sun, 19 Oct 2014 18:56:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5C183E089D; Sun, 19 Oct 2014 18:56:28 +0000 (UTC) Received: from mail-vc0-f195.google.com (mail-vc0-f195.google.com [209.85.220.195]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 37AEFE086E for ; Sun, 19 Oct 2014 18:56:26 +0000 (UTC) Received: by mail-vc0-f195.google.com with SMTP id hy10so882475vcb.10 for ; Sun, 19 Oct 2014 11:56:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=EBD4Y+dAdHijmThNpKAj7Olm6Hd0QN1aqpCsbMvqkqk=; b=tG+LiPNph0pX5XSBtoD3QAuWhWoNzkOqZHLAse8+Z43DquJfNcXbqI9elES8Pt4QFV AWJsQWLQT41ul+32UJfgyMvXn3+/OZowFhhZN0nwXjFQ4w7RspjNuBwv7OV/7bPnBYZj YZadmFn05tqjX5iUNcvR7OapJz4UTNBfIIT61Y8U/ydTuY+m16NPa/1VTl+oK6/8eXT7 5OOLnY8wUIu1RTNWzbvcYaFK26pPTZTFFNUqGYtd5iUKBoCfMg/0auzCF8GPBAiF2dZI eAUYu3WcUyWBFkIJnlSEVY5x4ErVJRC3fsprqVI4vZR36rg+5Nj552E97qnkpBu6N4db A1mA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.52.165.68 with SMTP id yw4mr857257vdb.42.1413744986322; Sun, 19 Oct 2014 11:56:26 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.52.8.229 with HTTP; Sun, 19 Oct 2014 11:56:26 -0700 (PDT) In-Reply-To: References: <5442DAC8.2030106@thegeezer.net> <5442F17C.7040904@thegeezer.net> <5443A864.2030508@thegeezer.net> Date: Sun, 19 Oct 2014 14:56:26 -0400 X-Google-Sender-Auth: IRv7iliaD3M65mRQQMNWiTuolZw Message-ID: Subject: Re: [gentoo-user] Re: gigabyte mobo latency From: Rich Freeman To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 91be8f16-14a4-41ff-a98b-de8be28a92f7 X-Archives-Hash: 62cfb5ed0245bb4a9bda5bfdf4a04526 On Sun, Oct 19, 2014 at 12:41 PM, James wrote: > Even if we all end up migrating to systemd (which from plentiful complaints > from many very bright folks about the net and the lack of a clean, useful > documentation on systemd, it's likely to be a decade before systemd > stablizes and folks produce sufficiently useful documentation and examples) > cgroups does illuminate how things should work in a complex environment so > it still is worth it's weight in gold, before one attempts to master the > (systemd) beast. So, I realize there are many strong opinions regarding systemd, but this comes across a bit like, "one should be well-accustomed to building and operating a Linux-From-Scratch installation before one attempts to master the (Ubuntu) beast." Sure, all that auto-magic stuff does add complexity, but it does so with the goal of standardizing and automating this so that you can use the system without having to worry about all the details. If you are running a systemd service you can set the various cgroup controls like IO and CPU class/priority in the unit and it will take care of managing the cgroup for you. Certainly learning the nuts and bolts of how it all works is worthwhile - I wouldn't be running Gentoo if I felt otherwise. However, you really don't have to know how to build your own service manager to use one. As far as docs go - what specifically is unclear? Systemd is rapidly evolving so things do get out of date, but for the most part stuff like this can be found in man systemd.exec and such. Lennart's series of blog posts on system administration using systemd is a very good place to start. -- Rich