From: Bastian Bittorf <bittorf@bluebottle.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
openwrt-devel@lists.openwrt.org
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, Stable <stable@vger.kernel.org>
Subject: Re: [PATCH] b43: Increase number of RX DMA slots
Date: Tue, 19 Feb 2013 21:01:31 +0100 [thread overview]
Message-ID: <20130219200131.GL8730@medion.lan> (raw)
In-Reply-To: <51228ACF.3060500@lwfinger.net>
* Larry Finger <Larry.Finger@lwfinger.net> [18.02.2013 21:17]:
> (14e4:4315) units. I think the firmware and DMA can handle it. After
> all, all the TX rings have 256 slots. There is, however, a question
> of the memory. TX only acquires the buffers when needed, but RX has
> to get them in advance, thus 256 slots there will waste a lot of
> memory.
I did some testing with 256 slots and the
"b43-workaround-rx-fifo-overflow.patch" on a very slow board,
an i'am sure, that 128 slots are not enough. kernel-log is here:
http://intercity-vpn.de/files/openwrt/b43test.dmesg.txt
this was a normal download (100mb @ 1 megabyte/s), but if you
do some udp-magic (netperf) you run soon into trouble.
thanks for your work!
bye, bastian / wireless.subsignal.org / weimarnetz e.V.
next prev parent reply other threads:[~2013-02-19 20:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 3:01 [PATCH] b43: Increase number of RX DMA slots Larry Finger
2013-02-18 16:18 ` Rafał Miłecki
2013-02-18 16:55 ` Bastian Bittorf
2013-02-18 17:04 ` Larry Finger
2013-02-18 20:10 ` Larry Finger
2013-02-19 20:01 ` Bastian Bittorf [this message]
2013-02-19 5:52 ` David Miller
2013-02-19 9:42 ` David Laight
2013-02-19 9:57 ` Rafał Miłecki
2013-02-19 17:57 ` Larry Finger
2013-02-19 18:15 ` David Miller
2013-02-19 18:28 ` Larry Finger
2013-02-20 0:47 ` Julian Calaby
2013-02-20 2:42 ` Larry Finger
2013-02-20 6:26 ` Gábor Stefanik
2013-02-20 7:15 ` Larry Finger
2013-02-20 8:15 ` Bastian Bittorf
2013-02-20 15:49 ` Larry Finger
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=20130219200131.GL8730@medion.lan \
--to=bittorf@bluebottle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=stable@vger.kernel.org \
--cc=zajec5@gmail.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).