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 <c...@freebsd.org> 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 <sobo...@freebsd.org> > 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 <i...@bsdimp.com> 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 > >> _______________________________________________ > >> firstname.lastname@example.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to " > freebsd-current-unsubscr...@freebsd.org" > >> > >> > > _______________________________________________ > > email@example.com mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscr...@freebsd.org" > > _______________________________________________ firstname.lastname@example.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"