From owner-freebsd-current@freebsd.org Tue May 3 10:51:55 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66107B2BB08 for ; Tue, 3 May 2016 10:51:55 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7CA41391 for ; Tue, 3 May 2016 10:51:54 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id a17so31623632wme.0 for ; Tue, 03 May 2016 03:51:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=Ujx7YAP2obQljhwaiShSUJUYiXMYeWfK3FbFLwj3Rl4=; b=Rd20KmZZBVkzWo4ALRnEoHEFUfZy6lZbJ7f84Ho/7YIqI+QqD96otH2PIvMe4OUVT4 Ag4eai/XF6vjiD+hSrnQ6sOO5w61PiOCdRxC1U9OFDIhUiY+gUZ80AJh57zl56R/yUIH NLm6pBvR5S7kd2RJuqXl/Z+Eu0FoBqHY/6Q+XQhsJPy4l7xYHe9j2vGVzHh7UoFtBm2M fZVmbxm71t3M5U8E6i9eFZ0/DtV/qo8tUsakX05DdDYT+aNxC2mASTYN9sEYqaZSVJ8N BtErbbrSEVpAKH87RCoHwa/gSr/QRsSUdSww3QTZICYm8MTMtbLffgW6YwG8wxq9b6fV dETg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=Ujx7YAP2obQljhwaiShSUJUYiXMYeWfK3FbFLwj3Rl4=; b=ZYl8/6n5aAXkQZ1AVwYBwpGG/1v09Vd89u9kW30x1ktw9CjJI5mhnTz0ogA4qYOozZ 6W1rvMOlvdbw0X+RO9vc6rdYWae07v4MXDjRkE4VuSFUYJT0hYD2EymIHNSOdTlkDi+j 18RHHDfWYI9ytpod2N2vBwhf1mtgnH1REkp6pyZJKLVoHvzHAE15wfCJOiPb4s5OP3qz iJKpcEYM8s3xZrlYeenMPWEkuBnFcXBftd2A8xCalM/YZrwmWDHOQy3DHfsbOU7Xpvwj rPQ3JOQQGD76Zmkq3U8eGsyHuc8knVY4YkajWI7vmKttRxgWGup+pUsK799VRLi3MAoI aKrg== X-Gm-Message-State: AOPr4FXxIN/vmH/oLtd3YABTuMhJCw8lndNrlAa6zm9bgPTrrgnZyYp9H8GZZF/sBRMMKA== X-Received: by 10.28.53.193 with SMTP id c184mr25473918wma.93.1462272713349; Tue, 03 May 2016 03:51:53 -0700 (PDT) Received: from Johans-MacBook-Air.local (92-111-79-242.static.chello.nl. [92.111.79.242]) by smtp.googlemail.com with ESMTPSA id iv1sm3150016wjb.34.2016.05.03.03.51.51 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 03 May 2016 03:51:52 -0700 (PDT) Subject: Re: FreeBSD Quarterly Status Report - First Quarter 2016 (fwd) To: Warren Block References: Cc: freebsd-current@freebsd.org From: Johan Hendriks Message-ID: <38091325-b0c9-ac6d-d6e9-efc29c814e0a@gmail.com> Date: Tue, 3 May 2016 12:51:50 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Tue, 03 May 2016 10:51:55 -0000 Op 02/05/16 om 02:49 schreef Warren Block: > CAM I/O Scheduler > > Links > I/O Scheduling in FreeBSD's CAM Subsystem (PDF) URL: > https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf > The BSDCan 2015 Talk URL: https://www.youtube.com/watch?v=3WqOLolj5EU > > Contact: Warner Losh > > An enhanced CAM I/O scheduler has been committed to the tree. By > default, this scheduler implements the old behavior. In addition, an > advanced adaptive scheduler is available. Along with the scheduler, > SATA disks can now use Queued Trims with devices that support them. > Details about the new scheduler are available in the I/O Scheduling in > FreeBSD's CAM Subsystem article (PDF) or from the BSDCan 2015 talk. > > The adaptive I/O scheduler is disabled by default, but can be enabled > with options CAM_ADAPTIVE_IOSCHED in the kernel config file. This > scheduler allows favoring reads over writes (or vice versa), > controlling the IOPs, bandwidth, or concurrent operations (read, > write, > trim), and permits the selection of static or dynamic control of these > operations. In addition, a number of statistics are collected for > drive > operations that are published via sysctl. One advanced use for the > adaptive I/O scheduler is to compensate for deficiencies in some > consumer-grade SSDs. These SSDs exhibit a performance cliff if too > much > data is written to them too quickly due to internal garbage > collection. > Without the I/O scheduler, read and write performance drop > substantially once garbage collection kicks in. The adaptive I/O > scheduler can be configured to monitor read latency. As read latency > climbs, the I/O scheduler reduces the allowed write throughput, within > limits, to attempt to maximize read performance. A simple use of the > adaptive I/O scheduler would be to limit write bandwidth, IOPs or > concurrent operations statically. > > Future work on the I/O scheduler will be coupled with improvements to > the upper layers. The upper layers will be enhanced to communicate how > urgent I/O requests are. The I/O scheduler will inform the upper > layers > of how full the I/O queues are, so less urgent I/O can be submitted to > the lower layers as quickly as possible without overwhelming the lower > layers or starving other devices of requests. > > This project was sponsored by Netflix. > __________________________________________________________________ I updated my source today, but CAM_ADAPTIVE_IOSCHED yields an error about an unknown option. If I use CAM_NETFLIX_IOSCHED the kernel compiles. Is the name CAM_NETFLIX_IOSCHED changing to CAM_ADAPTIVE_IOSCHED? regards Johan