All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: YIN Wei <yinwei168@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	mattias.nissler@gmx.de, stefano.brivio@polimi.it
Subject: Re: [PATCH] mac80211: improve PID rate control mechanism by avoiding rate oscillation problem
Date: Wed, 29 Feb 2012 09:31:03 +0100	[thread overview]
Message-ID: <1330504263.4714.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAFxU49=OASHEDc2m8BfCGD6_gHcr6SFaap+b9ZnErWhNWFG8oQ@mail.gmail.com> (sfid-20120229_031816_008358_36E52A04)

On Wed, 2012-02-29 at 12:17 +1000, YIN Wei wrote:
> From: Wei YIN

You want an email address here,

> Improve PID rate control mechanism by solving the rate oscillation
> problem. Current PID mechanism is based on a PID  controller which
> tries to minimise the difference between the frame loss ratio (FLR)
> and the target FLR. Therefore it is straight forward that it increases
> to a higher rate when the FLR is less than the target without thinking
> whether the higher rate can be supported. If the higher rate cannot be
> supported, significant FLR will occur, which causes the mechanisms to
> decrease the rate sharply. The proposed approach only updates the rate
> when the proposed rate by the PID controller can achieve better
> throughput than the old rate. This patch applies to kernel 3.3.0.
> Signed-off-by: Wei YIN

and here.

Also since you sent as HTML, it never made it to the list and can't be
applied as a patch, care to resend?

johannes



       reply	other threads:[~2012-02-29  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFxU49=OASHEDc2m8BfCGD6_gHcr6SFaap+b9ZnErWhNWFG8oQ@mail.gmail.com>
2012-02-29  8:31 ` Johannes Berg [this message]
2012-02-29 12:14 [PATCH] mac80211: improve PID rate control mechanism by avoiding rate oscillation problem YIN Wei
2012-02-29 12:45 ` Felix Fietkau
2012-02-29 12:59 ` Julian Calaby
2012-02-29 13:02   ` Julian Calaby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1330504263.4714.2.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mattias.nissler@gmx.de \
    --cc=stefano.brivio@polimi.it \
    --cc=yinwei168@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.