From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 31 16:21:45 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8A400649 for ; Wed, 31 Jul 2013 16:21:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1B2DD2A4B for ; Wed, 31 Jul 2013 16:21:44 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id n11so807445wgh.9 for ; Wed, 31 Jul 2013 09:21:43 -0700 (PDT) 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=VX4yHWTrloOR5Xj1HDdbpzBwVV/ggQk8wU6atL9WfgE=; b=DV362LGptG82Ai313cZgegSTyU/+05vrwIXHiI5R52TAXagFyVOjQau4JCbIR7hM0O 41ORqoezkuK3dr4kDL0hKrwWJaGVNSkNGxIci71Cy4ZJfu2H26fI4fMyE7eiPzoKozB7 oMLacWqBc9LgqUpIezVyr7UNz/gUaDpBEcme0n7nVyGCbejsFNeL2MkCGrLjN243QMY8 hfCxqsC6yCSkW4wrz7PAZAIyMprXG3Au7lmTUcy6dYKP5Mncn1M9P6VTCcoNg1/5z7+F B6iw0sr0444Opxg6T6fElEzz2PbtZGDUcITrCDRqbV363oDFK74CBAtlFnCJ+iLC+CuV AM4w== MIME-Version: 1.0 X-Received: by 10.180.82.196 with SMTP id k4mr4964102wiy.0.1375287703259; Wed, 31 Jul 2013 09:21:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Wed, 31 Jul 2013 09:21:43 -0700 (PDT) In-Reply-To: References: Date: Wed, 31 Jul 2013 09:21:43 -0700 X-Google-Sender-Auth: jgRdNccfQKr9sdLhrMDgI5ds9AI Message-ID: Subject: Re: Chenchong's work on net80211_ratectl From: Adrian Chadd To: Chenchong Qin 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: Wed, 31 Jul 2013 16:21:45 -0000 Boo! Do you have another update? -adrian On 24 July 2013 06:44, Adrian Chadd wrote: > On 24 July 2013 06:38, Chenchong Qin wrote: >> >> My pleasure! >> >> It's also against HEAD. >> >> Thanks! > > Ok. This is looking great! > > Next - we need to update the rate control API to now populate an rc > array rather than just returning the rix. > > This is the tricky part - as we're going to have to modify all the > drivers that use the rate control API to use this. > Which is fine, as there's only a handful. It's just annoying. > > Then we have to provide the rate control information during frame > _completion_, so the rate control code knows which transmission rates > succeeded or failed. I'm still not sure what to do about it here. > Maybe do something like Linux and attach TX rate control and > completion information as an mbuf tag? > > _Then_ we can start doing interesting thing with it. :) > > > > -adrian