From: Bruno Randolf <br1@einfach.org>
To: ath5k-devel@lists.ath5k.org
Cc: Bob Copeland <me@bobcopeland.com>,
Arnd Hannemann <hannemann@nets.rwth-aachen.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath5k-devel] ath5k IBSS mode high latency
Date: Fri, 5 Mar 2010 09:32:25 +0900 [thread overview]
Message-ID: <201003050932.26034.br1@einfach.org> (raw)
In-Reply-To: <b6c5339f1003030906jaa47f8dld615865b52bf19a1@mail.gmail.com>
On Thursday 04 March 2010 02:06:26 Bob Copeland wrote:
> By the way, I did notice that if we fail to map DMA
> buffers we can leak tx descriptors, but this is unlikely
> to be the cause.
i have also seen the problem that we can run out of memory when there is a lot
of traffic (UDP) to forward. i have that fairly reproducable here.
bruno
prev parent reply other threads:[~2010-03-05 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 16:07 ath5k IBSS mode high latency Arnd Hannemann
2010-03-03 17:06 ` Bob Copeland
2010-03-04 13:57 ` Arnd Hannemann
2010-03-05 0:32 ` Bruno Randolf [this message]
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=201003050932.26034.br1@einfach.org \
--to=br1@einfach.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=hannemann@nets.rwth-aachen.de \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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).