Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Apr 2016 11:30:05 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Maxim Sobolev <sobomax@freebsd.org>
Cc:        "Conrad E. Meyer" <cem@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Heads up
Message-ID:  <CANCZdfpKmk4%2BmS-xNN0cdCyOb=GN2P5%2BESZpOWwJCTZPkWpm8w@mail.gmail.com>
In-Reply-To: <CAH7qZfuA56CxMo9B6-1%2B7hhvugGiAMJG0_O3qW57chesSA_1Kw@mail.gmail.com>
References:  <CANCZdfpnYnVrvhNagYUT9RhAuC1AMCrxh=GCt8RKT0bqxuJybw@mail.gmail.com> <CAH7qZftspY=i5MaQ6sNg5L5XXBN7gfCuAMO-NZt=7Qp5zo6u_w@mail.gmail.com> <CAG6CVpXKZJFi7f=uxoXbc-MoHwd6JqZMwh-6m%2BGZvJ9JT95ZOA@mail.gmail.com> <CAH7qZfuA56CxMo9B6-1%2B7hhvugGiAMJG0_O3qW57chesSA_1Kw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 15, 2016 at 11:25 AM, Maxim Sobolev <sobomax@freebsd.org> 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 <cem@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 <sobomax@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 <imp@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
>> >> _______________________________________________
>> >> 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"
>>
>>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpKmk4%2BmS-xNN0cdCyOb=GN2P5%2BESZpOWwJCTZPkWpm8w>