From: Jouni Malinen <jouni.malinen@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Paged SKBs v/s copybreak.
Date: Tue, 25 Jan 2011 00:51:35 +0200 [thread overview]
Message-ID: <1295909495.4581.50.camel@jm-desktop> (raw)
In-Reply-To: <4D3DFE49.7050500@candelatech.com>
On Mon, 2011-01-24 at 14:33 -0800, Ben Greear wrote:
> So, I am hoping for some guidance from the core ath9k folks. Should
> I attempt to fix my copybreak patch for non pci busses and re-post
> it?
My preference would be to use multiple RX buffers to receive long frames
(chain RX descriptors with rs_more). I sent a preliminary patch for
doing that. Unfortunately, I have not had time to complete this and
probably in the near future. However, if someone has time available, it
should be simple to get the initial version into suitable condition
(just add support for the EDMA case where there may extra meta data in
the beginning of the first RX buffer). That should already be enough to
get the patch in and handle skb taking more than a page allocation
issue. As the next step, mac80211 could be optimized to be able to
handle A-MSDU RX without having to re-allocate and copy the received
long buffers.
The main benefit of this approach is that only the really long frames
(A-MSDU RX) would suffer from the need to re-allocate and copy and even
that A-MSDU RX case can be optimized by extending mac80211. In addition,
this should make it easy to take larger A-MSDU size limit into use
without extra cost for throughput reasons in the future.
- Jouni
next prev parent reply other threads:[~2011-01-24 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 22:33 [ath9k-devel] Paged SKBs v/s copybreak Ben Greear
2011-01-24 22:51 ` Jouni Malinen [this message]
2011-01-24 22:59 ` Felix Fietkau
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=1295909495.4581.50.camel@jm-desktop \
--to=jouni.malinen@atheros.com \
--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.