From owner-freebsd-current@freebsd.org Fri May 19 17:27:37 2017 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 C8EDAD73579; Fri, 19 May 2017 17:27:37 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 917821647; Fri, 19 May 2017 17:27:36 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id F042D2615C0; Fri, 19 May 2017 19:27:33 +0200 (CEST) Subject: Re: make concurrency kit a module To: Adrian Chadd , Warner Losh Cc: Baptiste Daroussin , freebsd-current , "freebsd-arch@freebsd.org" References: <20170518055352.bflapm6mmfhgl4y4@ivaldir.net> From: Hans Petter Selasky Message-ID: <3c4c6496-9a80-a45b-b3a1-9cdfb094c0a2@selasky.org> Date: Fri, 19 May 2017 19:25:34 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 19 May 2017 17:27:37 -0000 On 05/19/17 17:34, Adrian Chadd wrote: > On 17 May 2017 at 23:37, Warner Losh wrote: >> On Wed, May 17, 2017 at 11:53 PM, Baptiste Daroussin wrote: >>> On Wed, May 17, 2017 at 06:04:09PM -0700, Adrian Chadd wrote: >>>> https://reviews.freebsd.org/D10778 >>>> >>> >>> Except there are plans to use it elsewhere. Many areas may be improved using it. >>> >>> Having it as a module would mean some devs might refrain from using it because >>> there is no waranty for it to be there >>> >>> Areas like VFS and network stack could have a good benefice from using it. >>> >>> Out of curiousity what size is saved? >> >> I'd planned on using it newbus to solve the lifetime issues we have >> with device_t's.... > > I'm happy with things using it in base outside of the linuxkpi. > > I'm just trying to push back on the "death by a thousand cuts" that > the IOT platforms face for size constraints. There's plenty of stuff > in the base kernel that storage challenged platforms don't need but > they're not introduced or kept as modules. > > It's 2017 and people /are still/ making embedded boards with 8MB of NOR flash. Hi, Please make sure that the CK can still be built as part of the kernel, if you plan to make it a module by default. --HPS