From owner-freebsd-wireless@FreeBSD.ORG Fri Sep 9 11:29:50 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8B1D1065679 for ; Fri, 9 Sep 2011 11:29:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gw0-f49.google.com (mail-gw0-f49.google.com [74.125.83.49]) by mx1.freebsd.org (Postfix) with ESMTP id 9D3998FC1B for ; Fri, 9 Sep 2011 11:29:50 +0000 (UTC) Received: by mail-gw0-f49.google.com with SMTP id 1so1264280gwb.36 for ; Fri, 09 Sep 2011 04:29:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=lK9GaDZE5ZDJheCqEdsXbitwdN5b8U3Wja0ZE5mOaek=; b=EFrBn2O39uu1H1FrXkR7wj/dobp//EVa6mZUasVXfos+lUD+HKGpxceqQ7J20jjkZC aX/76RVNZu+24pjB32K43vjZnNZuQSG38zjIARDvveuAesiSgnDbjpT7BXt6wA10YnlK qf2FB8dYVwqhBrQW/e7AaR/GJ9QVpNeCV0Jog= MIME-Version: 1.0 Received: by 10.236.144.193 with SMTP id n41mr10975348yhj.78.1315567790417; Fri, 09 Sep 2011 04:29:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.103.6 with HTTP; Fri, 9 Sep 2011 04:29:50 -0700 (PDT) Date: Fri, 9 Sep 2011 19:29:50 +0800 X-Google-Sender-Auth: vW5iaV5SsaWRgaUzIGY3vUWF2Ng Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Ath 11n TX update X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 11:29:50 -0000 Hi, I've fixed a bunch of TX related bugs which has made TX quite a bit more stable. There's still one bug which is causing TX timeouts. I've added some further debugging to the TX code. I'd appreciate it if people would be willing to update and test this code. I think it's almost ready to be used in station mode. The lack of filtered frames handling is going to make hostap support of power-saving stations perform quite badly. The only real problems right now: * The lack of BAR frame sending means that there will be traffic pauses in certain situations. What I may do is flip on the printfs again so you'll at least see -when- the BAR frames would be TXed. * The rate control code is still suboptimal and looks to be the primary reason why TCP TX throughput doesn't remain very stable. It's still usable though! Thanks, Adrian