From: Felix Fietkau <nbd@openwrt.org>
To: linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com
Subject: Re: [PATCH 01/10] ath9k: use a separate data structure for rx buffers
Date: Thu, 10 Oct 2013 23:08:20 +0200 [thread overview]
Message-ID: <52571744.3040306@openwrt.org> (raw)
In-Reply-To: <1381407312-72719-1-git-send-email-nbd@openwrt.org>
On 2013-10-10 2:15 PM, Felix Fietkau wrote:
> There's no shared code for handling both rx and tx buffers, and tx
> buffers require a lot more metadata than rx buffers.
> Using a separate data structure for rx reduces memory usage and improves
> cache footprint.
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Sorry, this one's missing a chunk. Will send v2.
- Felix
prev parent reply other threads:[~2013-10-10 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 12:15 [PATCH 01/10] ath9k: use a separate data structure for rx buffers Felix Fietkau
2013-10-10 12:15 ` [PATCH 02/10] ath9k_hw: remove direct accesses to channel mode flags Felix Fietkau
2013-10-10 12:15 ` [PATCH 03/10] ath9k_hw: remove IS_CHAN_B() Felix Fietkau
2013-10-10 12:15 ` [PATCH 04/10] ath9k_hw: remove IS_CHAN_OFDM() Felix Fietkau
2013-10-10 12:15 ` [PATCH 05/10] ath9k_hw: simplify channel flags Felix Fietkau
2013-10-10 12:15 ` [PATCH 06/10] ath9k: make ath9k_cmn_update_ichannel static Felix Fietkau
2013-10-10 12:15 ` [PATCH 07/10] ath9k: move channel change code to ath_set_channel Felix Fietkau
2013-10-10 12:15 ` [PATCH 08/10] ath9k: remove sc->config.cabqReadyTime Felix Fietkau
2013-10-10 12:15 ` [PATCH 09/10] ath9k: make ath9k_uses_beacons static Felix Fietkau
2013-10-10 12:15 ` [PATCH 10/10] ath9k_hw: remove references to hw->conf Felix Fietkau
2013-10-10 21:08 ` Felix Fietkau [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=52571744.3040306@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.