From owner-freebsd-current@freebsd.org Fri Apr 15 17:30:07 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 2E32FAECCEE for ; Fri, 15 Apr 2016 17:30:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (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 EAFB1149E for ; Fri, 15 Apr 2016 17:30:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x242.google.com with SMTP id s2so15925212iod.3 for ; Fri, 15 Apr 2016 10:30:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=h0Nh67RmhKcfmEJWApAeFG0+CHPtuSpGqZLf6/Lz7Wg=; b=L1GqYbnSOv+fuk/tVDy8A9tyfp9GZMCWqck7hnPQ/CkEF/D77qbTbrh1tCnV5vVAHn kWey4YKeDqkeyDTD/XfoHTVrs3dvLRbQhoy9diKzlt2XHP+7yNmlK+mvg6QppfyXk94s VO38f4Ukqxjn9Y6NbJFcgZeYQnPo8I5WboAJT6YNJgr08Si09ijJnbLP/m5qkyKkcVcy uv+53tCP8zE85PYxucMNWH3aVC8ughKbPt244hc1D08vO5Ez+7E2aPeJZ4tffHLJBuyw EDwoXFAWHq26wawpQix6RaKTMNUmDvvX8jsZ0AcVMyIlvnaC1WpNzLHXJZjvc8zYhemt TkrA== 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=h0Nh67RmhKcfmEJWApAeFG0+CHPtuSpGqZLf6/Lz7Wg=; b=HaOgW8hXwvp2q/WHe6Z1UTG+H0qbY31D51yIchWOd7HlNiZdNylYw0+jso4qEyzg6/ F/u+KOUSd1IMj4Ww+OnWF8lQf1YL+TxiFrATnVSUtpYzMBTSVD9rDjks5M6ynYKIPq/2 GVRagg0wZIBoEvLMd0QSTiScy2lADCXWYglKZgs5a/ukNOSP1d4bTs/Co+lRmeQMKskE YmOsmd7HRVu8/nnO/o4+iGRLnQ80Dtfxi/FdS5Xd42h1MPFlin59ZbEyU4wg7aFus8El inHKFhhWITu4b6nxXxXZIxnIcYs5ZTFONKxtsEQE8j1MaUSDnXpTB5Ru4CakzOPgwMWp Nyog== X-Gm-Message-State: AOPr4FW6S+CdH0HISLX2f/Dbg67YaPI4Aq3+xCdfOpLCNWUprt8N+MEVT9Hryhozzyp0DVK7+S50zuoOKsiQrw== MIME-Version: 1.0 X-Received: by 10.107.133.151 with SMTP id p23mr23972364ioi.16.1460741406095; Fri, 15 Apr 2016 10:30:06 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.79.104.197 with HTTP; Fri, 15 Apr 2016 10:30:05 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: Date: Fri, 15 Apr 2016 11:30:05 -0600 X-Google-Sender-Auth: Yht0Y8Hu91Q7FkUvHzJKPGzywnQ Message-ID: Subject: Re: Heads up From: Warner Losh To: Maxim Sobolev Cc: "Conrad E. Meyer" , 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:30:07 -0000 On Fri, Apr 15, 2016 at 11:25 AM, Maxim Sobolev wrote: > 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. > The name isn't obscene or offensive. > 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. > Probably not. This is a weak argument. It's a descriptive use of the word, and not being used to market or sell video streaming services or DVD rental by mail. > 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. > Also a horrible name. It's a generic I/O scheduler. It can do lots of things. I keep saying that, and categorically refuse to name the more expansive scheduler anything that's so limiting. Warner > 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" >> >> >