All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, Bastian Bittorf <bittorf@bluebottle.com>,
	Stable <stable@vger.kernel.org>
Subject: Re: [PATCH] b43: Increase number of RX DMA slots
Date: Mon, 18 Feb 2013 14:10:55 -0600	[thread overview]
Message-ID: <51228ACF.3060500@lwfinger.net> (raw)
In-Reply-To: <CACna6rwLgE+o2mcRTemLFAqzdsEoA9Xyx8GyEQTh5qbv1iZ04A@mail.gmail.com>

On 02/18/2013 10:18 AM, Rafał Miłecki wrote:
> 2013/2/18 Larry Finger <Larry.Finger@lwfinger.net>:
>> Bastian Bittorf reported that some of the silent freezes on a Linksys WRT54G
>> were due to overflow of the RX DMA ring buffer, which was created with 64
>> slots. That finding reminded me that I was seeing similar crashed on a netbook,
>> which also has a relatively slow processor. After increasing the number of
>> slots to 128, runs on the netbook that previously failed now worked; however,
>> I found that 109 slots had been used in one test. For that reason, the number
>> of slots is being increased to 256.
>
> So probably ideal solution is to use 128 *and* fix the driver's
> failing on overflow ;)
>
> Did you try it on some old device? Just for sure firmware&DMA will
> handle it correctly.

I tested on BCM4318 (which is pretty old), and two different BCM4312 (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 agree that there be two patches, depending on Bastian's testing. The slot size 
change can be backported to stable.

Larry


  parent reply	other threads:[~2013-02-18 20:10 UTC|newest]

Thread overview: 25+ 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  3:01 ` Larry Finger
2013-02-18 16:18 ` Rafał Miłecki
2013-02-18 16:18   ` Rafał Miłecki
2013-02-18 16:55   ` Bastian Bittorf
2013-02-18 16:55     ` Bastian Bittorf
2013-02-18 17:04     ` Larry Finger
2013-02-18 20:10   ` Larry Finger [this message]
2013-02-19 20:01     ` Bastian Bittorf
2013-02-19 20:01       ` Bastian Bittorf
2013-02-19  5:52 ` David Miller
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  6:26                 ` Gábor Stefanik
2013-02-20  7:15                 ` Larry Finger
2013-02-20  8:15                   ` Bastian Bittorf
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=51228ACF.3060500@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bittorf@bluebottle.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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 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.