From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Implement rx copy-break.
Date: Sun, 09 Jan 2011 07:18:57 -0700 [thread overview]
Message-ID: <4D29C3D1.4020804@openwrt.org> (raw)
In-Reply-To: <AANLkTim0=1wpPGPDZZzVjO0u_jvv5knA2=v4b-dTfRFq@mail.gmail.com>
On 2011-01-09 7:15 AM, Bj?rn Smedman wrote:
> I think we should also consider the added stability/saneness with this
> patch. I for one would be willing to live with some extra cpu load if
> that means the unstoppable rx dma problem can be contained (all the
> time).
I don't think this patch has anything to do with the rx dma stop issue.
- Felix
WARNING: multiple messages have this Message-ID (diff)
From: Felix Fietkau <nbd@openwrt.org>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: Ben Greear <greearb@candelatech.com>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath9k: Implement rx copy-break.
Date: Sun, 09 Jan 2011 07:18:57 -0700 [thread overview]
Message-ID: <4D29C3D1.4020804@openwrt.org> (raw)
In-Reply-To: <AANLkTim0=1wpPGPDZZzVjO0u_jvv5knA2=v4b-dTfRFq@mail.gmail.com>
On 2011-01-09 7:15 AM, Björn Smedman wrote:
> I think we should also consider the added stability/saneness with this
> patch. I for one would be willing to live with some extra cpu load if
> that means the unstoppable rx dma problem can be contained (all the
> time).
I don't think this patch has anything to do with the rx dma stop issue.
- Felix
next prev parent reply other threads:[~2011-01-09 14:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 15:33 [ath9k-devel] [PATCH] ath9k: Implement rx copy-break greearb at candelatech.com
2011-01-08 15:33 ` greearb
2011-01-09 0:20 ` [ath9k-devel] " Felix Fietkau
2011-01-09 0:20 ` Felix Fietkau
2011-01-09 0:36 ` [ath9k-devel] " Ben Greear
2011-01-09 0:36 ` Ben Greear
2011-01-09 0:41 ` [ath9k-devel] " Felix Fietkau
2011-01-09 0:41 ` Felix Fietkau
2011-01-09 1:06 ` [ath9k-devel] " Ben Greear
2011-01-09 1:06 ` Ben Greear
2011-01-09 14:15 ` [ath9k-devel] " Björn Smedman
2011-01-09 14:15 ` Björn Smedman
2011-01-09 14:18 ` Felix Fietkau [this message]
2011-01-09 14:18 ` Felix Fietkau
2011-01-09 15:35 ` [ath9k-devel] " Björn Smedman
2011-01-09 15:35 ` Björn Smedman
2011-01-09 18:13 ` [ath9k-devel] " Jouni Malinen
2011-01-09 18:13 ` Jouni Malinen
2011-01-09 20:14 ` [ath9k-devel] " Christian Lamparter
2011-01-09 20:14 ` Christian Lamparter
2011-01-09 20:24 ` [ath9k-devel] " Felix Fietkau
2011-01-09 20:24 ` Felix Fietkau
2011-01-10 12:40 ` [ath9k-devel] " Jouni Malinen
2011-01-10 12:40 ` Jouni Malinen
2011-01-10 4:32 ` [ath9k-devel] " Ben Greear
2011-01-10 4:32 ` Ben Greear
2011-01-09 8:00 ` [ath9k-devel] " Gabor Juhos
2011-01-09 8:00 ` Gabor Juhos
2011-01-09 17:49 ` [ath9k-devel] " Ben Greear
2011-01-09 17:49 ` Ben Greear
2011-01-10 7:14 ` [ath9k-devel] " Gabor Juhos
2011-01-10 7:14 ` Gabor Juhos
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=4D29C3D1.4020804@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.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.