linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Mattias Nissler <mattias.nissler@gmx.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Stefano Brivio <stefano.brivio@polimi.it>,
	linux-wireless@vger.kernel.org
Subject: Re: [patch 4/9] mac80211: Make PID rate control algorithm the default
Date: Mon, 17 Dec 2007 09:48:59 -0500	[thread overview]
Message-ID: <20071217144859.GB3121@tuxdriver.com> (raw)
In-Reply-To: <1197885374.7514.6.camel@localhost>

On Mon, Dec 17, 2007 at 10:56:14AM +0100, Mattias Nissler wrote:
> 
> On Mon, 2007-12-17 at 02:09 +0100, Johannes Berg wrote:
> > > That was my original proposal, but during a recent discussion John
> > > suggested not to remove rc80211-simple right now, as it's currently
> > > almost working for a lot of people. John, any suggestions?
> > 
> > Those people can fix the bitrate at 1M if the pid algorithm becomes
> > problematic, that's what simple currently does in practice.
> 
> Agreed. So what flavour of this patch do you want? John?

My "Spidey sense" tells me it would be good to keep the old one around
for a little while... :-)

Besides, as we have seen recently people often get quite upset when
you remove a feature that they perceive to be working for them --
no matter how much better the alternative may be.  It would be better
to give them some warning.

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2007-12-17 15:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17  0:19 [patch 0/9] Rate control rework mattias.nissler
2007-12-17  0:20 ` [patch 5/9] mac80211: Introduce rate behaviour learning algorithm mattias.nissler
2007-12-17  0:20 ` [patch 9/9] mac80211: Publish rc80211_pid parameters in debugfs mattias.nissler
     [not found] ` <20071217002056.351743954@gmx.de>
2007-12-17  0:49   ` [patch 4/9] mac80211: Make PID rate control algorithm the default Johannes Berg
2007-12-17  0:50     ` Stefano Brivio
2007-12-17  0:54       ` Johannes Berg
2007-12-17  0:57         ` Stefano Brivio
2007-12-17  1:09           ` Johannes Berg
2007-12-17  9:56             ` Mattias Nissler
2007-12-17 14:48               ` John W. Linville [this message]
2007-12-17 17:42                 ` Johannes Berg
2007-12-17  9:51       ` Mattias Nissler
2007-12-17  9:54 ` [patch 0/9] Rate control rework Mattias Nissler
2007-12-17 14:05 ` Johannes Berg
2007-12-17 20:59   ` Mattias Nissler
2007-12-18 13:18     ` Johannes Berg
     [not found] ` <20071217002056.677829348@gmx.de>
2007-12-17 16:43   ` [patch 8/9] debugfs: Revamp debugfs_create_{u,x,s}{8,16,32,64} to support signed integers Johannes Berg
2007-12-17 21:05     ` Mattias Nissler
     [not found] <20071217012517.882216322@gmx.de>
     [not found] ` <20071217012550.213561122@gmx.de>
2007-12-17 11:52   ` [patch 4/9] mac80211: Make PID rate control algorithm the default Johannes Berg
2007-12-17 21:12     ` Mattias Nissler
2007-12-17 15:02   ` John W. Linville
2007-12-17 20:06     ` Stefano Brivio
2007-12-17 20:41       ` John W. Linville
2007-12-17 21:16         ` Stefano Brivio
2007-12-18 12:49           ` Johannes Berg
2007-12-18 20:01             ` Mattias Nissler
2007-12-19 16:05               ` Johannes Berg

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=20071217144859.GB3121@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mattias.nissler@gmx.de \
    --cc=stefano.brivio@polimi.it \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).