From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-03-iad.dyndns.com (mxout-238-iad.mailhop.org [216.146.32.238]) by lists.bufferbloat.net (Postfix) with ESMTP id 726642E020D for ; Sun, 27 Feb 2011 08:01:59 -0800 (PST) Received: from scan-02-iad.mailhop.org (scan-02-iad.local [10.150.0.207]) by mail-03-iad.dyndns.com (Postfix) with ESMTP id 5E53983644B for ; Sun, 27 Feb 2011 16:01:32 +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-03-iad.dyndns.com (Postfix) with ESMTP id 0002283644A for ; Sun, 27 Feb 2011 16:01:30 +0000 (UTC) Received: by qwb7 with SMTP id 7so2869699qwb.16 for ; Sun, 27 Feb 2011 08:01:29 -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=LYbF5bOY02Ix4d9x1hY/uWPOm2YxA3eEI1xQYbgJec4=; b=Fw9A4PFtVTS21Lfl38jmZiiZtFa7rTPeP5aR7mGxU2IWg2FthdfM/Zj4j2k3+y/A4y adzB/DKF/2E5GKQ12Z0rezZ3uYDWbkU1xaUKzAIBv/cpB8Q7+rUsHIl+JnwMq6Prm9Zi 2V0aT33Mdpib89RKxfE3l3c9tM0EjlU9XplqQ= 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=nEcPV6HJ6ISgE2dRiihIbrQPKPPa17LYh/3uSemjE2PR6wQIFWqLrumNkkIyGSemtA 6W5nZO2KLZHA40Y68jZ0+6k86wdcGkClBLMJnFrlqLzTtDN70BAnr0BB34BrZ9tJP+ed 3sUj6nWy1Wv/yB0KNyt9Gs+49B9XCbvqq8TTs= MIME-Version: 1.0 Received: by 10.229.246.209 with SMTP id lz17mr3365288qcb.271.1298822487639; Sun, 27 Feb 2011 08:01:27 -0800 (PST) Received: by 10.229.89.85 with HTTP; Sun, 27 Feb 2011 08:01:27 -0800 (PST) In-Reply-To: <8739n9ii7z.fsf@cruithne.co.teklibre.org> References: <20110225222210.GA3618@tuxdriver.com> <87fwr9jxya.fsf@cruithne.co.teklibre.org> <8739n9ii7z.fsf@cruithne.co.teklibre.org> Date: Sun, 27 Feb 2011 17:01:27 +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 16:01:59 -0000 On Sun, Feb 27, 2011 at 4:56 PM, Dave T=C3=A4ht wrote: > Sedat Dilek writes: > >> 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---- > >>> 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) >>> > >> These "debloat guys" are fast :-). =C2=A0I was just preparing my >> build-system (which I normally use to debianize linux-next kernels). >> Any other recommendation for kernel-config options? =C2=A0For example: >> linux-next has already CONFIG_NET_SCH_CHOKE (but I have unset it). > > Enable CHOKe. > > The HZ value change is due to my worry that we've smashed latency so > much in the driver/mac layer that it's interacting with the higher > layers somewhat badly... So we need to add more hooks to the servo loops > involved in order to have a normal HZ. > >> Which commits are in debloat-testing GIT but not in linux-next tree? > > The current list was in the release announcement. More on the way > (mostly embedded drivers at this point) git pull early and often! > >> Are you planning debloat feature for 2.6.39? > > Depends on how many testers we get and what the results are. > > I feel the eBDP stuff will not be ready during this release cycle. SFB > and CHOKe are in net-next, so, probably. Various driver patches - > particularly those that increase the available dynamic range via > ethtool, (e.g lowering the bottommost TX queue limit to, like, 4, > especially for home gateways) may make it out if people look harder into > the issue. > >> >> - Sedat - > > -- > Dave Taht > http://nex-6.taht.net > OK, thanks for the explanations. Concerning "more drivers": What would I have to do to modify ath5k? I looked into the ath9k patch in debloat-testing GIT and it was to mod some (TX/BUF) values only. Not sure if ath9k is/was "well" prepared or only a good choice by the testers/committers as they own such a device. - Sedat -