From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 11 08:35:54 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53C991065673 for ; Mon, 11 Jun 2012 08:35:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2ACAB8FC18 for ; Mon, 11 Jun 2012 08:35:54 +0000 (UTC) Received: by dadv36 with SMTP id v36so5300825dad.13 for ; Mon, 11 Jun 2012 01:35:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=9c9g00ErM8xc73Q2dAJ8TSdjeXxyUJuGurR7jzVidQw=; b=LuwJ9YmKZH+WEefRelJyJ0M4K4pbOvbFxB+OfRx5JrcwquP1CUz/DgnsqtSgqokDD5 8KFZaruaw7pdpDtjh/XHqWSNm1qBxhEZh2Ks0noJbIqy1aXoVY6JcML0blZ9NHddtteM ei/w2ZiQCX7uampa51rESL4bVzitS6YjzKaTv8y1fDdps5XE9IsvjMd6Q72g7Ngx55Ij yuOLnLEbilFXSpdeijr7Ds7tFAa4Vp18sc+QTEN+NkbO3O2mBYyObqlLwswr9lAJ5VPQ ibsXAwo9k6zhZ9ONg+59dIIJZ4iQVTbem4QlT84+7mfla4WxuD6SR1lFmiPz8i6hhCrr Md3A== MIME-Version: 1.0 Received: by 10.68.226.226 with SMTP id rv2mr25468274pbc.101.1339403753752; Mon, 11 Jun 2012 01:35:53 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.91.18 with HTTP; Mon, 11 Jun 2012 01:35:53 -0700 (PDT) Date: Mon, 11 Jun 2012 01:35:53 -0700 X-Google-Sender-Auth: -c9dlTj6C6_7Vqb4yTy8ml-I4aA Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [heads up] please test -HEAD ath(4) 802.11n! 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: Mon, 11 Jun 2012 08:35:54 -0000 Hi all, I've just done some major surgery to the ath(4) TX path to fix TX throughput issues on SMP. The commit history has all the sordid details. I'd really appreciate it if people could test this out in STA and AP mode with INVARIANTS/WITNESS enabled. I'd like to ensure I haven't introduced LORs or any locking issues. As always, positive feedback is also useful (just so I know the code is tested.) I'd really like to get this thrashed out so I can move onto implementing the management frame prioritisation, power save and filtered frame support. Once that's done, I'll enable 802.11n by default. Thanks again! Adrian