All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@cozybit.com>
Cc: linux-wirelss <linux-wireless@vger.kernel.org>,
	open80211s <devel@lists.open80211s.org>
Subject: Re: [PATCH 3/6] mac80211: ieee80211_queue_stopped returns reasons
Date: Tue, 09 Apr 2013 11:37:26 +0200	[thread overview]
Message-ID: <1365500246.8465.5.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAG6hwVOAwtngWU3uEueG7hZX3z5dxLLc8c8-Vd7Q+e93wM-UaQ@mail.gmail.com> (sfid-20130408_215754_514729_5AC29991)

On Mon, 2013-04-08 at 12:57 -0700, Thomas Pedersen wrote:

> > That seems racy? Even asking whether it's stopped is racy though, what
> > are you even trying to accomplish?
> 
> Yeah, that's why I'd like to get the reason the first time.
> 
> _h_mesh_fwding() checks whether the outgoing queue is stopped, to
> avoid piling frames on the pending queue if the outgoing medium is
> busy. I guess the idea was to avoid queueing frames faster than the
> hardware could unload them. Maybe this doesn't actually happen, but we
> can be a little bit smarter about when to drop forwarded frames. Like
> if skbs are just being added to the outgoing queue, we probably
> shouldn't.

Technically I guess that can happen if your inbound link is better than
the outbound one? But it'll depend on the AC parameters etc. too.

However it seems that ieee80211_queue_stopped() is actually kinda broken
and should only return the 'driver-stopped' reason to start with. If you
fix that, it's probably good enough for you. I don't think in patch 4
you should drop frames for scanning, for example.

johannes


  reply	other threads:[~2013-04-09  9:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 18:06 [PATCH 1/6] mac80211: unset FC retry bit in mesh fwding path Thomas Pedersen
2013-04-08 18:06 ` [PATCH 2/6] mac80211: exclude multicast frames from BA accounting Thomas Pedersen
2013-04-09  9:47   ` Johannes Berg
2013-04-10 22:15     ` Thomas Pedersen
2013-04-08 18:06 ` [PATCH 3/6] mac80211: ieee80211_queue_stopped returns reasons Thomas Pedersen
2013-04-08 18:32   ` Antonio Quartulli
2013-04-08 18:37   ` Johannes Berg
2013-04-08 19:30     ` Thomas Pedersen
2013-04-08 19:38       ` Johannes Berg
2013-04-08 19:57         ` Thomas Pedersen
2013-04-09  9:37           ` Johannes Berg [this message]
2013-04-10 17:36             ` Thomas Pedersen
2013-04-10 18:16               ` Johannes Berg
2013-04-08 18:06 ` [PATCH 4/6] mac80211: limit mesh forwarding drops Thomas Pedersen
2013-04-08 18:06 ` [PATCH 5/6] mac80211: stringify another plink state Thomas Pedersen
2013-04-09  9:48   ` Johannes Berg
2013-04-08 18:06 ` [PATCH 6/6] mac80211: avoid mesh peer rate update warning Thomas Pedersen
2013-04-09  9:38   ` Johannes Berg
2013-04-09  9:42     ` Johannes Berg
2013-04-10 17:38       ` Thomas Pedersen
     [not found] ` <1782507887.154.1365455855469.JavaMail.mail@webmail12>
2013-04-08 21:27   ` [PATCH 5/6] mac80211: stringify another plink state Joe Perches
2013-04-08 22:19     ` Joe Perches
2013-04-09  9:39 ` [PATCH 1/6] mac80211: unset FC retry bit in mesh fwding path 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=1365500246.8465.5.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=devel@lists.open80211s.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=thomas@cozybit.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.