From owner-freebsd-current@freebsd.org Fri Apr 15 16:39:49 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 8DB23AEEA62 for ; Fri, 15 Apr 2016 16:39:49 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi0-f65.google.com (mail-oi0-f65.google.com [209.85.218.65]) (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 5ED021715; Fri, 15 Apr 2016 16:39:49 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi0-f65.google.com with SMTP id v67so14412794oie.0; Fri, 15 Apr 2016 09:39:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc; bh=U4kDwc/mwthcqI/pXjREmEW8MpwgfmDNpg5XGJErYjQ=; b=S6lQcQL3dmKYSlkQ7hRmgBrRgQyNcH5/Ylxgc2nId+JBi6OX/9KPcOnNPFU2nqfFir Bfic/fKmb11gartCJKetLqsVZx9rkFR5/f1qK78p5shB19Za0WaiUCIZs6f+tCcgzfag l6QiXbRPOtfOMqoZf7wMlEYTGE5IlhExr29+2lF9R2O6e7RSTmWph0b8XbLeVV62RC1+ 9QFL5vP+2wybNryLkOZjUZvM4/XILaP6eTyjjxp+f3C+hxLEq94KxndiVDzUF55Jb2vM FgtpKGKJNjzv8ukkY95TVzNkYc/I7hGusHoAHlhr9SBUF0HxOhZ9Q8O+yt2m0Uyqtj/u FlVA== X-Gm-Message-State: AOPr4FXqNNXgt+B/BEWoEoNOJNOc/iBrSsrAHdQs172VA7u3XpRGs5tCfKdDYCRXoDtPVA== X-Received: by 10.157.13.170 with SMTP id 39mr11838142ots.134.1460737322978; Fri, 15 Apr 2016 09:22:02 -0700 (PDT) Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com. [209.85.218.44]) by smtp.gmail.com with ESMTPSA id p1sm1181150obn.22.2016.04.15.09.22.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Apr 2016 09:22:02 -0700 (PDT) Received: by mail-oi0-f44.google.com with SMTP id y204so128832383oie.3; Fri, 15 Apr 2016 09:22:02 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.157.52.70 with SMTP id v64mr11645018otb.72.1460737322263; Fri, 15 Apr 2016 09:22:02 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.157.22.215 with HTTP; Fri, 15 Apr 2016 09:22:02 -0700 (PDT) In-Reply-To: References: Date: Fri, 15 Apr 2016 09:22:02 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Heads up From: Conrad Meyer To: Maxim Sobolev Cc: Warner Losh , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 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: Fri, 15 Apr 2016 16:39:49 -0000 Max, If you implement a new IO scheduler you can name it whatever you like. "NG" isn't any more meaningful than "Netflix." Best, Conrad On Fri, Apr 15, 2016 at 9:13 AM, Maxim Sobolev wrote: > Great, work Warner, thanks! Small note, though. The CAM_IOSCHED_NETFLIX > seems like a quite poor name for a kernel option. IMHO there is no good > reason for polluting it with the name of the company that sponsored the > development. I don't think we have any precedents of doing this unless the > option is related to a piece of hardware that the company makes, and it's > not the case here. Apart from "coolness" factor as far as I understand that > _NETFLIX suffix does not give any tangible benefit for anybody reading > kernel config and trying to understand what this option actually does. > CAM_IOSCHED_SSDNG or something would be better IMHO. Just my $0.02. > > -Max > > On Thu, Apr 14, 2016 at 3:42 PM, Warner Losh wrote: > >> The CAM I/O scheduler has been committed to current. This work is described >> in https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the >> default scheduler doesn't change the default (old) behavior. >> >> One possible issue, however, is that it also enables NCQ Trims on ada SSDs. >> There are a few rogue drives that claim support for this feature, but >> actually implement data corrupt instead of queued trims. The list of known >> rogues is believed to be complete, but some caution is in order. >> >> Warner >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"