From owner-freebsd-current@freebsd.org Fri Apr 15 17:25:41 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 65E33ADAC17 for ; Fri, 15 Apr 2016 17:25:41 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (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 338611DB4 for ; Fri, 15 Apr 2016 17:25:41 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-ob0-x22e.google.com with SMTP id bg3so67847852obb.1 for ; Fri, 15 Apr 2016 10:25:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sippysoft-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=At8jr1j1QTpPqJQgChSIe5bKeW86OV88eiHzRfmeV7w=; b=0iqBX0TG9ccbBrqrjuUk2j9mTfFIf2+Q0bEBcAZktDoj37zQL2CZIS1jx15CzIiZiz 2CUxfW4j7vHijd1qucMNvoqIUn4kA8bnF9OcJSgs1wqDnu57CFBTelXTTwVE+62iJzpT B15/pgDToWrcGy9dmBHr4DESVrUpxtr78yHKDZBZyhOj/uFYu1gIXJQ9c6xsg8eO80UM CESWprqbMWvCx3Yh+0lC5Sz2z6eO0PyOo7f7U//oRwOs9iEynceXKf0wRCniE0escFxf MdWG83hahbw13Lpvcrg3Jr96h8baTVK1s25ssJeIZh6fApPfxHf7SZy1ihUPWON1eFCe bXYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=At8jr1j1QTpPqJQgChSIe5bKeW86OV88eiHzRfmeV7w=; b=VtYnhoc565BT6DBYyLFIB98ajOObgFOwtC1rlqUoMeVsIs5q5sFeocSLfqqh+p2xjn q3Sw/UHn7CtpJGweSRL7W2iFLlxdmJpWlXD4dU8OjBW6rjEAEjzvaX2B7X+LuusFN8aC nMtUONMHd8VyC94987O9ut9p2XKnl0qn6vYLbCNSoiRmYXweR/IPxHSCt+wztmJ2/xlM YOqAMAQk6Suin2rg+nc2Lj46u9QtQGTt8J6U63zaWmgq/fiOEtX1NJ0NqsqpqDlzTO31 3Nn5AKBgTSO4gHtUBaFGEVXbPkkD2MZnDj5qmxnO9q79FAYXFszIDdGf4PwCidt3bTD4 WgTA== X-Gm-Message-State: AOPr4FXu/UJzUeUfbGkfk54lKaFyGB2ZKgTkX1iU/+3u8b7OSzJULWqTGHh/tQbCkbSWXHgt6uLYT5zgh0EaUPnm MIME-Version: 1.0 X-Received: by 10.182.58.36 with SMTP id n4mr11655797obq.2.1460741140463; Fri, 15 Apr 2016 10:25:40 -0700 (PDT) Sender: sobomax@sippysoft.com Received: by 10.157.37.123 with HTTP; Fri, 15 Apr 2016 10:25:40 -0700 (PDT) In-Reply-To: References: Date: Fri, 15 Apr 2016 10:25:40 -0700 X-Google-Sender-Auth: AlU5ko-4iIDgdowhSS5WfiiP5fM Message-ID: Subject: Re: Heads up From: Maxim Sobolev To: "Conrad E. Meyer" Cc: Warner Losh , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 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 17:25:41 -0000 Conrad, yes, you can, but sticking it into FreeBSD source tree IMHO restricts your options somewhat. If it's your private code you can easily put F-world into it and nobody obviously cares apart from your co-workers and your boss. Would probably be considered highly inappropriate by most to merge it into a public one, so "whatever your like" rule has its limits. Also, apart from being not very suggestive as to what this option actually does, let's not forget that "Netflix" is probably registered as a trademark and whatnot in North America at least, if not worldwide. I am not a lawyer, but I suspect using it might have some ramifications for our ability to name things using this name. If "SSDNG" is not a good name, I'd suggest coming up with some other name that is neutral and also has some hints as to its functionality. For example, CAM_IOCHED_LOW_LAT or something. On Fri, Apr 15, 2016 at 9:22 AM, Conrad Meyer wrote: > 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" > >