From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-02-ewr.dyndns.com (mxout-106-ewr.mailhop.org [216.146.33.106]) by lists.bufferbloat.net (Postfix) with ESMTP id D3B9A2E0053 for ; Sun, 27 Feb 2011 07:38:48 -0800 (PST) Received: from scan-01-ewr.mailhop.org (scanner [10.0.141.223]) by mail-02-ewr.dyndns.com (Postfix) with ESMTP id 1B69973CB13 for ; Sun, 27 Feb 2011 15:38:20 +0000 (UTC) X-Spam-Score: -1.0 (-) X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 209.85.216.43 Received: from mail-qw0-f43.google.com (mail-qw0-f43.google.com [209.85.216.43]) by mail-02-ewr.dyndns.com (Postfix) with ESMTP id 7CE3573C8FE for ; Sun, 27 Feb 2011 15:38:18 +0000 (UTC) Received: by qwb7 with SMTP id 7so2860330qwb.16 for ; Sun, 27 Feb 2011 07:38:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=MDKE+nvQi79pJyO68cTSwUXJfTn7b+31GYd4EMgnNIs=; b=Jb9hVcgFERc3Jb1+xBjLwmYzuUO8JQPSmCd4JFqp6Qf+zbO2Gj/fEs7ZbGzQG9swqy mkFrUOHCOVm1Y9EWLvcyJQNzSkH9sKwex0uwwZWul5zlDhf8w8Q7gn7gkgINsLcc9aG2 vhNqPTslDouzWHOpQFv5ivDgC5cZ8zLi9AGW4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=B2hocqzPAUD97kleqjwHtRruT9eOTqiSuE9LTv6BDacfPkm/qZ7YnkPKimmwiJmaxj p6zOHQq+qmuDROptPTBCsmIKKlyiWxjROZ53OSQD/YT6L1yb2OYdx6dU6Sx9KUqnZ0ze SJbVOz+0QyTlsQJOr6JUPQuEDwQrTonXVqJnc= MIME-Version: 1.0 Received: by 10.229.240.66 with SMTP id kz2mr3379802qcb.233.1298821097597; Sun, 27 Feb 2011 07:38:17 -0800 (PST) Received: by 10.229.89.85 with HTTP; Sun, 27 Feb 2011 07:38:17 -0800 (PST) In-Reply-To: <87fwr9jxya.fsf@cruithne.co.teklibre.org> References: <20110225222210.GA3618@tuxdriver.com> <87fwr9jxya.fsf@cruithne.co.teklibre.org> Date: Sun, 27 Feb 2011 16:38:17 +0100 Message-ID: Subject: Re: ANNOUNCE: debloat-testing kernel git tree From: Sedat Dilek To: =?UTF-8?Q?Dave_T=C3=A4ht?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, bloat-devel@lists.bufferbloat.net, linux-kernel@vger.kernel.org X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list Reply-To: sedat.dilek@gmail.com List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2011 15:38:49 -0000 On Sun, Feb 27, 2011 at 4:31 PM, Dave T=C3=A4ht wrote: > > Sedat Dilek writes: > >> On Fri, Feb 25, 2011 at 11:22 PM, John W. Linville >> wrote: >>> Announcement >>> >>> The bufferbloat project [1] is pleased to announce the availability >>> of the debloat-testing Linux kernel git tree: >>> >>> =C2=A0 git://git.infradead.org/debloat-testing.git > > ----snip---- > >> Hi, >> >> it should be "localversion-debloat" in the commit-subject in [1] (not >> "localversion-wireless") :-). =C2=A0"-db" as suffix is IMHO not very >> meaningful... Why not add simply a suffix called "-debloat"? =C2=A0(Anyw= ay, >> I will revert this patch because I don't want to have any suffix added >> automatically.) >> >> I have several other questions, but I start compiling first and test >> this debloat kernel. > > Excellent. At moment I would recommend building "low latency preempt > desktop" kernels with a high HZ value (400 or 1000), enabling highres > timers, and compiling in SFB as a module. (I'd like the default for SFB > to be "m" rather than "n", too) > >> >> Regards, >> - Sedat - >> >> [1] "Add localversion-wireless to identify builds from this tree." >> http://git.infradead.org/debloat-testing.git/commit/3f9bdb4f44b076feda72= d353d8ad717831416f36 >> _______________________________________________ >> Bloat-devel mailing list >> Bloat-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/bloat-devel > > -- > Dave Taht > http://nex-6.taht.net > These "debloat guys" are fast :-). I was just preparing my build-system (which I normally use to debianize linux-next kernels). Any other recommendation for kernel-config options? For example: linux-next has already CONFIG_NET_SCH_CHOKE (but I have unset it). Which commits are in debloat-testing GIT but not in linux-next tree? Are you planning debloat feature for 2.6.39? - Sedat -