From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Switching to 4.174.64.19 firmware for G-PHY cards?
Date: Thu, 03 Mar 2011 09:52:40 -0600 [thread overview]
Message-ID: <4D6FB948.2000902@lwfinger.net> (raw)
In-Reply-To: <AANLkTi=nPjvDvN+EF08oey=PCKWH0=u2R0X813-GNsnh@mail.gmail.com>
On 03/03/2011 01:55 AM, Rafa? Mi?ecki wrote:
> 824 line is:
> [struct b43_dmaring *]ring = kzalloc(sizeof(*ring), GFP_KERNEL);
>
> Does anyone know why sometime we allocate 60b and sometimes 96b? It's
> always the same struct... :| Could be STA vs. AP related but... how? I
> don't see a way.
It depends on whether CONFIG_B43_DEBUG is defined.
As you hint at later, Chris's memory problem is not due to a direct allocation
problem, but is due to indirect allocation of skb or some other type of buffer.
Why they leak on his system, and not on mine is a puzzle.
Larry
next prev parent reply other threads:[~2011-03-03 15:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 12:21 Switching to 4.174.64.19 firmware for G-PHY cards? Rafał Miłecki
2010-12-07 12:28 ` Rafał Miłecki
2010-12-07 15:32 ` Larry Finger
2010-12-07 19:21 ` Hauke Mehrtens
2011-03-01 13:33 ` Rafał Miłecki
2011-03-02 0:11 ` chris at martin.cc
2011-03-02 0:20 ` Rafał Miłecki
2011-03-02 3:30 ` chris at martin.cc
2011-03-02 9:58 ` Rafał Miłecki
2011-03-02 10:52 ` Rafał Miłecki
2011-03-02 11:22 ` Jonas Gorski
2011-03-02 12:20 ` chris at martin.cc
2011-03-02 22:00 ` Larry Finger
2011-03-02 23:02 ` chris at martin.cc
2011-03-03 4:43 ` chris at martin.cc
2011-03-03 7:58 ` Rafał Miłecki
2011-03-03 11:50 ` Rafał Miłecki
2011-03-03 23:49 ` chris at martin.cc
2011-03-07 12:35 ` Rafał Miłecki
2011-03-04 0:37 ` chris at martin.cc
2011-03-07 12:26 ` Rafał Miłecki
2011-03-08 1:12 ` chris at martin.cc
2011-03-07 13:12 ` Rafał Miłecki
2011-03-07 16:41 ` Rafał Miłecki
2011-03-08 1:25 ` chris at martin.cc
2011-03-08 13:26 ` Rafał Miłecki
2011-03-09 0:44 ` chris at martin.cc
2011-03-09 0:47 ` Rafał Miłecki
2011-03-09 0:47 ` chris at martin.cc
2011-03-03 4:55 ` chris at martin.cc
2011-03-02 23:00 ` chris at martin.cc
2011-03-02 12:14 ` chris at martin.cc
2011-03-02 13:12 ` Rafał Miłecki
2011-03-02 23:12 ` Jonas Gorski
2011-03-03 3:40 ` chris at martin.cc
2011-03-03 7:55 ` Rafał Miłecki
2011-03-03 15:52 ` Larry Finger [this message]
2011-03-03 5:34 ` chris at martin.cc
2011-03-03 4:23 ` chris at martin.cc
2011-03-02 10:08 ` Rafał Miłecki
2011-03-02 12:17 ` chris at martin.cc
2011-03-03 3:44 ` chris at martin.cc
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=4D6FB948.2000902@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.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 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.