From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 2 17:30:55 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5B4D5C48 for ; Fri, 2 Aug 2013 17:30:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E29692224 for ; Fri, 2 Aug 2013 17:30:54 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id hi8so803828wib.3 for ; Fri, 02 Aug 2013 10:30:51 -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=FB+Fhv5XuWsdk0ETOgacWM9ZC6BcNkbjXIADClhL0c4=; b=AapdfIQTJo2WXILVpzk5zt1CxOdBjwje2Dy4hfIFCYebBgDBcFMtJO3lpxNlHEiqNC nEcTtU2WwXeJImZ9IRPqBRBmElMFZKfboHrX7WpDxQUVNuFvoZy2DxXAnDoSA9/P1oZ+ FrLZ++hPSerSSRxtnnuzfldNvet9ecJDiTOo/HMgYfEmu3CKbfHHyZVa1yK3t4/GYChN 9JBgM5eHCiRPWgKj5cMBRwoxV5vWFlYDkdBZNpjK5sNFAL9BE68BNNawXRVT3R5DaPh0 /P5iV9WJh4XwZeirdBQY9UFZ5ntty6b/d1H6++V5l2Orqm2zZ9GO2N1HCpx+L26Dl7Tz cvjA== MIME-Version: 1.0 X-Received: by 10.194.11.67 with SMTP id o3mr5851590wjb.0.1375464651887; Fri, 02 Aug 2013 10:30:51 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Fri, 2 Aug 2013 10:30:51 -0700 (PDT) In-Reply-To: References: Date: Fri, 2 Aug 2013 10:30:51 -0700 X-Google-Sender-Auth: DQ301wZkoYSP0M3K_gUateQ2BN0 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: Fri, 02 Aug 2013 17:30:55 -0000 Well just remember you can always ask me/us questions! What's your latest diff against -HEAD? Maybe I can start looking at including parts of it in the tree. -adrian On 2 August 2013 09:17, Chenchong Qin wrote: > Hi! > > These days, I'm taking a further look at what Linux done for the > _completion_ of a > frame. Some updates will be posted here later. > > And, with ir_rates, we can return/fill an rc array rather than just > returning the rix. > > Thanks! > > Chenchong > > > > > > On Thu, Aug 1, 2013 at 12:21 AM, Adrian Chadd wrote: >> >> 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 > >