linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Bruno Randolf <br1@einfach.org>,
	Jonathan Guerin <jonathan@guerin.id.au>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	ath5k-devel <ath5k-devel@venema.h4ckr.net>,
	nbd@openwrt.org
Subject: Re: ath5k: Weird Retransmission Behaviour
Date: Wed, 8 Dec 2010 11:56:07 -0500	[thread overview]
Message-ID: <20101208165607.GE2423@tuxdriver.com> (raw)
In-Reply-To: <AANLkTi=95mO085Y1PJ3brMMpHa=QvkxSB3SUpQysvKr+@mail.gmail.com>

On Wed, Dec 08, 2010 at 11:45:39AM -0500, Bob Copeland wrote:
> On Wed, Dec 8, 2010 at 11:08 AM, Bob Copeland <me@bobcopeland.com> wrote:
> > On Mon, Dec 6, 2010 at 3:14 AM, Bruno Randolf <br1@einfach.org> wrote:
> >> But it seems weird that there are so many retransmissions. The default maximum
> >> numbers of retransmissions should be 7 for short frames and 4 for long frames
> >> (dot11[Short|Long]RetryLimit), and this is what is set as defaults in mac80211
> >> (local->hw.conf.short_frame_max_tx_count). Seems we are getting many
> >> retransmissions from minstel, i added some debug prints:
> >>
> >
> > I posted a patch for this about a week ago to linux-wireless.
> >
> > AFAICT minstrel doesn't use these configuration parrameters
> > at all (but PID does).
> >
> > --
> > Bob Copeland %% www.bobcopeland.com
> >
> 
> Found the patch:
> 
> https://patchwork.kernel.org/patch/359722/

Are you posting that for merging?  Or just for testing?

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2010-12-08 17:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06  6:30 ath5k: Weird Retransmission Behaviour Jonathan Guerin
2010-12-06  8:14 ` Bruno Randolf
2010-12-06  9:36   ` [ath5k-devel] " Nick Kossifidis
2010-12-06 10:53     ` Sedat Dilek
2010-12-07  2:29       ` Bruno Randolf
2010-12-07  1:17     ` Jonathan Guerin
2010-12-08  8:06       ` Bruno Randolf
2010-12-08  8:12         ` Jonathan Guerin
2010-12-06 18:01   ` Björn Smedman
2010-12-07  1:19     ` Jonathan Guerin
2010-12-07  1:12   ` Jonathan Guerin
2010-12-07  2:34     ` Bruno Randolf
2010-12-08 16:08   ` Bob Copeland
2010-12-08 16:45     ` Bob Copeland
2010-12-08 16:56       ` John W. Linville [this message]
2010-12-08 17:06         ` Bob Copeland
2010-12-08 17:11           ` Bob Copeland
2010-12-08 17:50             ` Sedat Dilek
2010-12-08 21:36               ` Bob Copeland
2010-12-08 21:53     ` Jonathan Guerin
2010-12-09  9:21       ` Helmut Schaa
2010-12-09 12:38         ` Bob Copeland
2010-12-09 14:34           ` Jonathan Guerin
2010-12-09 17:00             ` Bob Copeland
2010-12-09 22:41               ` Jonathan Guerin
2010-12-06  9:38 ` Nick Kossifidis
2010-12-07  1:18   ` Jonathan Guerin

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=20101208165607.GE2423@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=br1@einfach.org \
    --cc=jonathan@guerin.id.au \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=nbd@openwrt.org \
    /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).