From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 21 20:41:00 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5019106566C for ; Mon, 21 Nov 2011 20:41:00 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 31E088FC18 for ; Mon, 21 Nov 2011 20:40:59 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so9394147bkb.13 for ; Mon, 21 Nov 2011 12:40:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Xv8xuVEr1RmfuQBYHHNYpXG0oED7Tsv3Q/S+pUUoIDo=; b=mT6Qrj8zlkMTuWnLV7ihyx2RvpN/pXWRm6POeyMspuJXPoiJ/DjXuJXLvuBapKftIp mx3bnlIPjaS9zyllGZR97U7K+oCVVuA+aHU57SZmpnzxkoXD37hUs1SyxJWJNIPGecTH Fe6BqdESI8COnfrAIhP/2OdZDqrD4tKG+fbWI= MIME-Version: 1.0 Received: by 10.204.10.81 with SMTP id o17mr16047390bko.65.1321908058788; Mon, 21 Nov 2011 12:40:58 -0800 (PST) Received: by 10.223.88.72 with HTTP; Mon, 21 Nov 2011 12:40:58 -0800 (PST) In-Reply-To: References: Date: Mon, 21 Nov 2011 14:40:58 -0600 Message-ID: From: Adam Vande More To: Stefan Bethke Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Limiting disk I/O by jail or uid? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2011 20:41:00 -0000 On Mon, Nov 21, 2011 at 1:58 PM, Stefan Bethke wrote: > > Interesting, but it doesn't seem to offer limiting the I/O bandwidth > induced by a process or jail, or assigning different priorities, which > would need to be implemented in the ZFS or GEOM schedulers, I suppose. > Limiting CPU has long been the poor man's IO scheduler, and has usually worked pretty well for me but has required some trial and error. YMMV -- Adam Vande More