From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757429AbYIRXMf (ORCPT ); Thu, 18 Sep 2008 19:12:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757295AbYIRXMY (ORCPT ); Thu, 18 Sep 2008 19:12:24 -0400 Received: from yw-out-2324.google.com ([74.125.46.31]:14500 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757293AbYIRXMX (ORCPT ); Thu, 18 Sep 2008 19:12:23 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=uHFJdke4kphmgGFJ+ZD/j3pV8AtzxdlTGZrrKKba38/qE8kQCoaNdUTnp3tG7aE5uc CimchlQbfL2gOyQtebIxCY6CeVYN+6b0r6ivIYGRTH8e3bpTyDdsPBFmZ4Y51aNf/9QO rnBTpu7nur1/tCUnu55HsZuQ61ETRIkhPqei8= Message-ID: <43e72e890809181612s1b5016ebsf2b145def401b9cd@mail.gmail.com> Date: Thu, 18 Sep 2008 16:12:21 -0700 From: "Luis R. Rodriguez" To: "Steven Noonan" Subject: Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27 (rc5, rc6, probably others) Cc: "Ingo Molnar" , "ath9k-devel@lists.ath9k.org" , linux-wireless , LKML , "Luis Rodriguez" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <43e72e890809181134ybbec8fdxcb2a466aa17fe390@mail.gmail.com> <43e72e890809181142n7738cd99g522e6688e68d11ce@mail.gmail.com> <43e72e890809181344q416b5944w3332ee5a33db048c@mail.gmail.com> <20080918220102.GE7408@tesla> X-Google-Sender-Auth: 7237fd802bb9c5ec Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 18, 2008 at 4:08 PM, Steven Noonan > Will do! And actually, to be precise, the issue occurred not on the > rmmod, but on the following modprobe for ath9k. Ah -- it makes it even more interesting now.. >>> Which is far more important, I agree. It's annoying to get speeds >>> <802.11b on my pre-802.11n capable chipset and network. ;) >> >> Yeah exactly, I hope the work we do will get in for 27. We'll see. > > Linus has been fairly strict lately, so I am as uncertain as you are. > It really should get merged, because having 2.6.27 with [partially] > broken wireless networking is kind of stupid. In the worst case, isn't > it possible to do a revert to get the old aggregation crap back in? Well let us finish the patch first in a way that we are happy with it :) But yeah if its not merged distributions will probably just pick it up anyway. Luis