From owner-freebsd-wireless@FreeBSD.ORG  Fri Aug  2 16:17:04 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
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 DE5D8E1A;
 Fri,  2 Aug 2013 16:17:04 +0000 (UTC)
 (envelope-from qinchenchong@gmail.com)
Received: from mail-vb0-x234.google.com (mail-vb0-x234.google.com
 [IPv6:2607:f8b0:400c:c02::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 885EE2EEC;
 Fri,  2 Aug 2013 16:17:04 +0000 (UTC)
Received: by mail-vb0-f52.google.com with SMTP id f12so790230vbg.25
 for <multiple recipients>; Fri, 02 Aug 2013 09:17:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=sYHwg71w2ZZ8f4QOCKCRmmk/4ImQ1yaHJEbCYnw2GJc=;
 b=tyl62bS30E62/lnND60FymR/M7t91v1uo94+X0NefibwumW266s36KyhRj3IV79Bp1
 +SKPzbXgNe4M0TJlrMMnpwiI5aXOtN6QztX3cVEEGjG/jcbgYepo3IjUPAsJUr9A7miJ
 P7B1F+TNAfboAE/f6nIF5hVIiuUhy+kOrmlCEKncBrYhLxSWV0ut7bp68RINQfKmOGr9
 pb1S7RzUQYCcyvGBzIJXD84Kx1HrZnKbc4sVoKpgHyU4i4FYUcIJ2Ze9wSr1P/hBocCJ
 yR8vnQyDAAnt7vrdEoNtjEt/9VqgkdX284CGRN48vj+UI/I40J3p5YwTGlFBmvSxMVgY
 rKeQ==
MIME-Version: 1.0
X-Received: by 10.220.191.5 with SMTP id dk5mr2254294vcb.47.1375460223027;
 Fri, 02 Aug 2013 09:17:03 -0700 (PDT)
Received: by 10.220.57.142 with HTTP; Fri, 2 Aug 2013 09:17:02 -0700 (PDT)
In-Reply-To: <CAJ-VmonMjR5iVTMVN9532d+PqOXWNUoZvxPtQir5h=yGxU-XdQ@mail.gmail.com>
References: <CAFnsE3dYdPf5yGTFH683Q1Zh0mc-g+_YtCTraNNt28z2vBoSKw@mail.gmail.com>
 <CAJ-Vmom4sY7jcNwWmJkrDwfWjsok2fk8UEwTi5A=egj1JyerLw@mail.gmail.com>
 <CAFnsE3cyg=msBfQqqKUMmLABSL=j24VoMBwbBjxQ6b7Dyy7Mqg@mail.gmail.com>
 <CAJ-Vmo=k8NddAYyAJCkx4eOaA_8XsSxg6uKrdddx+gmeT+X9KA@mail.gmail.com>
 <CAFnsE3eaOyRcO3LXSi3L=jbzpyMv5Nt_jRGKt_mmA0WV-EV5vA@mail.gmail.com>
 <CAJ-VmokdxLhK5x6kO=jJzk-dv61EDK-ZgmndOimoyWWf76HiZA@mail.gmail.com>
 <CAJ-VmonMjR5iVTMVN9532d+PqOXWNUoZvxPtQir5h=yGxU-XdQ@mail.gmail.com>
Date: Sat, 3 Aug 2013 00:17:02 +0800
Message-ID: <CAFnsE3d9nG-X2b=z1srKfTtpxC3w5L+6Hg3TbOnAQrJN+t19GA@mail.gmail.com>
Subject: Re: Chenchong's work on net80211_ratectl
From: Chenchong Qin <qinchenchong@gmail.com>
To: Adrian Chadd <adrian@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 16:17:04 -0000

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 <adrian@freebsd.org> wrote:

> Boo!
>
> Do you have another update?
>
>
>
> -adrian
>
> On 24 July 2013 06:44, Adrian Chadd <adrian@freebsd.org> wrote:
> > On 24 July 2013 06:38, Chenchong Qin <qinchenchong@gmail.com> 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
>