linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2.6.33] mac80211: fix skb buffering issue
Date: Wed, 6 Jan 2010 12:32:05 +0100	[thread overview]
Message-ID: <20100106113205.GA1735@mail.wantstofly.org> (raw)
In-Reply-To: <20100105171603.GX6361@tuxdriver.com>

On Tue, Jan 05, 2010 at 12:16:03PM -0500, John W. Linville wrote:

> > Since I removed the master netdev, we've been
> > keeping internal queues only, and even before
> > that we never told the networking stack above
> > the virtual interfaces about congestion. This
> > means that packets are queued in mac80211 and
> > the upper layers never know, possibly leading
> > to memory exhaustion and other problems.
> > 
> > This patch makes all interfaces multiqueue and
> > uses ndo_select_queue to put the packets into
> > queues per AC. Additionally, when the driver
> > stops a queue, we now stop all corresponding
> > queues for the virtual interfaces as well.
> > 
> > The injection case will use VO by default for
> > non-data frames, and BE for data frames, but
> > downgrade any data frames according to ACM. It
> > needs to be fleshed out in the future to allow
> > chosing the queue/AC in radiotap.
> > 
> > Reported-by: Lennert Buytenhek <buytenh@marvell.com>
> > Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> > Cc: stable@kernel.org [2.6.32]
> > ---
> > I know it's late, and large, but still would be good to have in .33
> > since the issue is fairly serious.
> 
> Obviously I'd like to see some testing.  Lennert, does this
> patch resolve the issues you raised?

I had some QA done on 2.6.32 + this version of the patch (slightly
tweaked to make it apply to .32), and it solves the OOM issues we were
seeing, throughput looks good, the 8% more cpu that 2.6.32 uses
relative to 2.6.31 in the same forwarding test seems to be at least
partially taken care of by this patch, and there haven't been any
stability issues so far.

  parent reply	other threads:[~2010-01-06 11:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 17:00 [PATCH 2.6.33] mac80211: fix skb buffering issue Johannes Berg
2010-01-05 17:16 ` John W. Linville
2010-01-05 18:36   ` Lennert Buytenhek
2010-01-05 19:07   ` Felix Fietkau
2010-01-05 19:36     ` Lennert Buytenhek
2010-01-06 11:32   ` Lennert Buytenhek [this message]
2010-01-06  5:30 ` Larry Finger
2010-01-06 11:05   ` Johannes Berg
2010-01-06 18:16     ` Larry Finger
2010-01-06 11:33 ` Lennert Buytenhek
2010-01-06 21:26 ` Thomas Backlund
2010-01-06 21:51   ` Johannes Berg
2010-01-06 22:03     ` Felix Fietkau
2010-01-06 22:39       ` Thomas Backlund
2010-01-06 23:19         ` Thomas Backlund
2010-01-07  6:57           ` Johannes Berg
2010-01-07 10:41             ` Thomas Backlund
2010-01-06 22:31 ` Sedat Dilek
2010-01-07  4:10   ` Lennert Buytenhek
2010-01-07  9:24     ` Sedat Dilek
2010-01-07 14:01 ` mac80211: fix queue selection for packets injected via monitor interface Lennert Buytenhek
2010-01-07 15:45   ` Luis R. Rodriguez
2010-01-07 15:47     ` Lennert Buytenhek

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=20100106113205.GA1735@mail.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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).