From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-01-iad.dyndns.com (mxout-066-iad.mailhop.org [216.146.32.66]) by lists.bufferbloat.net (Postfix) with ESMTP id 871EF2E189C for ; Sun, 6 Feb 2011 10:09:45 -0800 (PST) Received: from scan-01-iad.mailhop.org (scan-01-iad.local [10.150.0.206]) by mail-01-iad.dyndns.com (Postfix) with ESMTP id E9EB66DD2B for ; Sun, 6 Feb 2011 18:09:43 +0000 (UTC) X-Spam-Score: 0.1 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 75.145.127.229 Received: from gw.co.teklibre.org (75-145-127-229-Colorado.hfc.comcastbusiness.net [75.145.127.229]) by mail-01-iad.dyndns.com (Postfix) with ESMTP id 69BBB6DCF0; Sun, 6 Feb 2011 18:09:38 +0000 (UTC) Received: from cruithne.co.teklibre.org (unknown [IPv6:2002:4b91:7fe5:2:21c:25ff:fe80:46f9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cruithne.co.teklibre.org", Issuer "CA Cert Signing Authority" (verified OK)) by gw.co.teklibre.org (Postfix) with ESMTPS id BF3E65E8AD; Sun, 6 Feb 2011 11:09:37 -0700 (MST) Received: by cruithne.co.teklibre.org (Postfix, from userid 1000) id DECD0121B7D; Sun, 6 Feb 2011 11:09:36 -0700 (MST) From: d@taht.net (Dave =?utf-8?Q?T=C3=A4ht?=) To: bloat-devel , bloat Organization: Teklibre - http://www.teklibre.com Date: Sun, 06 Feb 2011 11:09:36 -0700 Message-ID: <87ipwxf31b.fsf@cruithne.co.teklibre.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Bloat] branching the kernel, etc. X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Feb 2011 18:09:46 -0000 I'm posting this cross-list because I'd like to see development related issues move to the bloat-devel list long term, and I see several developer folk not on bloat-devel. I'd like to get some honest development happening. Branching the kernel, and maintaining it, seems to be a major headache. I'd like someone with cred in the kernel communities to step up, when it's needed. That person is not me. Anyone? The problems are: * Network device drivers are usually developed by small branches by vendor specific teams, then fed into one of three other branches (networking/wireless/staging), then into the mainline. Debloat work probably has to feed back through the same queues. It may well be the best places to get work done will be in the most relevant branch and mailing list. * The firmware blobs are completely non-transparent to anyone but the vendor. Software mechanisms (rate limiting) can evolve. Communicating effectively with the vendor may well require cross language skills. * Queuing disciplines can easily live outside the kernel * Openwrt lags behind the mainline often by a lot, carries a lot of out of tree packages, and yet there we can have the greatest effect. * There are people enthusiastic about new forms of traffic exchange, notably ledbat. Others are interested in various forms of TCP. Others are interested in IPv6. These cross wide swaths of the kernel, and would require a branch. There is roughly one person interested in each of these topics at present. My inclination is to wait for critical mass and get people to step up. * I'd like to have a European presence, and was thinking about not using github to manage repos. Actually, I kind of like stressing p2p development using ipv6, but that's me. * A build/test cluster would be nice. Just one fast 12 core box would be helpful. I liked the old handhelds.org model of shared development. * Different solutions for different OSes Related to all that is recruiting a BSD person, MS person, embedded person, etc into the herd of cats. -- Dave Taht http://nex-6.taht.net