All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Christian Mehlis <mehlis@inf.fu-berlin.de>,
	John W Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] ar9170usb: fix panic triggered by undersized rxstream buffer
Date: Wed, 24 Mar 2010 10:20:18 +0800	[thread overview]
Message-ID: <1269397218.4043.84.camel@debian> (raw)
In-Reply-To: <1269395940.5646.3.camel@jlt3.sipsolutions.net>

On Wed, 2010-03-24 at 09:59 +0800, Johannes Berg wrote:
> On Tue, 2010-03-23 at 21:51 +0100, Christian Lamparter wrote:
> > While ar9170's USB transport packet size is currently set to 8KiB,
> > the PHY is capable of receiving AMPDUs with up to 64KiB.
> > Such a large frame will be split over several rx URBs and
> > exceed the previously allocated space for rx stream reconstruction.
> > 
> > This patch increases the buffer size to 64KiB which is
> > in fact the phy & rx stream designed size limit.
> 
> That's a pretty high order allocation, you may want to paged allocation
> -- you'll end up doing a order 5 allocation here!

Yup, order-5 given the struct skb_shared_info overhead in __alloc_skb().
If the URBs are split over, you probably don't need to allocate such a
big chunk of memory in one go. You just need to connect them into a
paged skb later before pushing to mac80211. BTW, I've moved the
skb_linearize() from iwlwifi to mac80211. Will submit the patches today.

Thanks,
-yi


  reply	other threads:[~2010-03-24  2:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 20:51 [PATCH] ar9170usb: fix panic triggered by undersized rxstream buffer Christian Lamparter
2010-03-24  1:59 ` Johannes Berg
2010-03-24  2:20   ` Zhu Yi [this message]
2010-03-24 12:30     ` Christian Lamparter

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=1269397218.4043.84.camel@debian \
    --to=yi.zhu@intel.com \
    --cc=chunkeey@googlemail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mehlis@inf.fu-berlin.de \
    /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.