From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 24 13:44:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 14E69D4F for ; Wed, 24 Jul 2013 13:44:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A2593205B for ; Wed, 24 Jul 2013 13:44:38 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id j13so430958wgh.14 for ; Wed, 24 Jul 2013 06:44:37 -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=YukKAQnEiQFUlOu1/VT6ecjYdbCzrn0AjLR9rA0S3S0=; b=oYLdWAsI5sNc0i7v72kJyDWxGhbAgq0DdCS5PcrN15p4tpNwA4R7o/tFVkwL5gmcM2 5kxXK/O9m/RxZHSxVfflsw2tj7ajJ/ddGm7FG+HMtvQVdDceBkwntfttNdVvDVUzOh3Y kEa9MMGvr5Va5hFXL4ibBFsU3C9ljeabGwtLhxVM45qBeJqhAvGfjUjrtzBLrzplkBHe sGrWVSoiVYYhNc8YmjX1CvBKzjqQd3pPf+2HkkklqghIqcMt5P434eRBi4HNXovO0oee HhMsocbM43cRcuRFrMoiWPTC3iHsUzNhIVdUBvhz6RvbVm1oSsW6jhAmNWD4sIVtpcCq Dzbg== MIME-Version: 1.0 X-Received: by 10.180.39.212 with SMTP id r20mr2787203wik.30.1374673476939; Wed, 24 Jul 2013 06:44:36 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Wed, 24 Jul 2013 06:44:36 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Jul 2013 06:44:36 -0700 X-Google-Sender-Auth: OkOlk1nKy2KB9ys3Zafcnu6POrA 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, 24 Jul 2013 13:44:39 -0000 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