From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 22:55:33 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5A94106566C; Thu, 18 Nov 2010 22:55:33 +0000 (UTC) (envelope-from dnebdal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 53A898FC08; Thu, 18 Nov 2010 22:55:33 +0000 (UTC) Received: by iwn39 with SMTP id 39so4240617iwn.13 for ; Thu, 18 Nov 2010 14:55:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=RF7CCOjjlMdWa/4rvqXFs+lIae9Tv2SV06gC2Iwg5lw=; b=sg9Lue/o9Zt6bStriwYNlVqnQS2YrtrgKujqeiMr1Nkx+9Gm5XOyKRnTPAUPmC8+/+ u7LeESnuWOXHJgWbFDgZEGnxcOVQzTDWN89cyiRmIYuKoWtt5yHy0XOvs0887AYgM8bg cCG4fLaATSvJ2WRDRJgVFeFGYEGbw2SIP7em4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=fMlbe/aYao6kyPml/TI2MMaYrkjEeXAYlqYo6rXpVarqxEHJR5QiqLRIjkLBNo37yI gnYRMlLahOhJilq+0MPIIKXkIkg537iFPno/+ZVvRsAWd3XoFWIsrrte00ij69wZWLr9 Fb8VOwpOraNIIU2yUONOG4sos62SPreFwEawg= MIME-Version: 1.0 Received: by 10.231.34.3 with SMTP id j3mr1454614ibd.100.1290120931782; Thu, 18 Nov 2010 14:55:31 -0800 (PST) Received: by 10.231.58.202 with HTTP; Thu, 18 Nov 2010 14:55:31 -0800 (PST) In-Reply-To: <20101118170623.7f9c14f3@kan.dnsalias.net> References: <4CE50849.106@zedat.fu-berlin.de> <4CE52177.3020306@freebsd.org> <20101118182324.GA36312@freebsd.org> <20101118182852.GR63683@over-yonder.net> <20101118185635.GA43706@freebsd.org> <20101118170623.7f9c14f3@kan.dnsalias.net> Date: Fri, 19 Nov 2010 00:55:31 +0200 Message-ID: From: Daniel Nebdal To: FreeBSD Stable Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD@freebsd.org, Andriy Gapon , Current , "Matthew D. Fuller" , Alexander Best , freebsd-performance@freebsd.org, "O. Hartmann" Subject: Re: TTY task group scheduling X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 22:55:34 -0000 On Fri, Nov 19, 2010 at 12:06 AM, Alexander Kabaev wrote= : > On Thu, 18 Nov 2010 18:56:35 +0000 > Alexander Best wrote: > >> On Thu Nov 18 10, Matthew D. Fuller wrote: >> > On Thu, Nov 18, 2010 at 06:23:24PM +0000 I heard the voice of >> > Alexander Best, and lo! it spake thus: >> > > >> > > judging from the videos the changes are having a huge impact imo. >> > >> > Well, my (admittedly limited, and certainly anecdotal) experience is >> > that Linux's interactive response when under heavy load was always >> > much worse than FreeBSD's. =A0So maybe that's just them catching up to >> > where we already are =A0 ;) >> >> well...i tried playing back a 1080p vide files while doing >> `make -j64 buildkernel` and FreeBSD's interactivity seems far from >> perfect. > > One thing that just begs to be asked: since when decoding 1080p became > an interactive task? > Strictly speaking it isn't - but displaying it is a timing-sensitive task that isn't CPU- or I/O-bound, and scheduling-wise that probably makes it more like the "fast response when woken up" interactive tasks than a CPU-bound non-interactive process. Decoding it into another file on the disk is in the latter category, of course - but I don't think that's what he meant. :) More on topic - while this was a tiny patch for Linux, it seems like it would take more work for us, since I don't believe either of the schedulers handles task groups in the required way. The linux patch was just "create task groups automatically", since they already had some suitable logic for scheduling based on task groups in their CFS scheduler. We would have to (re-)add that first, which is non-trivial. -- Daniel Nebdal