From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 10 00:18:52 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 1D860E73 for ; Mon, 10 Dec 2012 00:18:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by mx1.freebsd.org (Postfix) with ESMTP id 9DE038FC08 for ; Mon, 10 Dec 2012 00:18:51 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id hj13so761529wib.13 for ; Sun, 09 Dec 2012 16:18:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=6V+mse0q0kAfBYefQCKGDCvPnOMEm8rY2JBFVwHUGJA=; b=bqL0wkF5N+V4QijvweR3/yYsNnJgDeblU/m6GswHP052SVioGK8MO0tI7GzWs1EzWG Qu5iqVNHMY9X5wrKSJjsMseEodF2CsKJ2RaeIkU2nSumIrLxwH7UWkHpkL5hQlMIlxRp 1ttXiHKQfZYRdfuu8kjUoyg0TFq057ZA9pJSz4+51vrNSc+gFgRWc7OssiOxYbMEHciN CtJMZR6AUG7AVwAlXrqREJh+c3igf+H41PwieiCyzFWgb8pZiiK7DvPkcYqz1Xqh2TOY k7knI+5VTodeIfK9B00uYhzntLtbYOPrv3mq6raqThK1MxXWhuzxIB26mYDDy6rsIP2x VJfw== MIME-Version: 1.0 Received: by 10.180.97.137 with SMTP id ea9mr8020336wib.13.1355098725205; Sun, 09 Dec 2012 16:18:45 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sun, 9 Dec 2012 16:18:45 -0800 (PST) In-Reply-To: References: <201205181133.57403.jhugo@meraka.csir.co.za> Date: Sun, 9 Dec 2012 16:18:45 -0800 X-Google-Sender-Auth: z0VTEhNLrubqsRGJhCpV2_yA29s Message-ID: Subject: Re: [ath] Degraded throughput - adhoc mode From: Adrian Chadd To: Johann Hugo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 10 Dec 2012 00:18:52 -0000 Ok, I've just taught the aggressive mode logic about IBSS. It's pretty dirty - I may cop some hate for enabling aggressive mode for IBSS as each IBSS node doesn't know about the overall voice/video data rates. That's how it works in AP mode - the AP tracks the traffic _it_ is sending/receiving and changes its configuration based on that. It can't take into account overlapping BSSes. In any case, can you just try that out in your lab and let me know how it goes? It's easy enough for me to disable the aggressive mode programming for IBSS mode once we better understand what's going on with the IBSS + WME programming. Thanks for being so patient with this! Adrian