Searched hist:"1 a04d59d3ec982689552077172893b6836def984" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/drivers/net/wireless/ath/ath9k/ |
| H A D | recv.c | diff 1a04d59d3ec982689552077172893b6836def984 Fri Oct 11 16:30:52 CDT 2013 Felix Fietkau <nbd@openwrt.org> ath9k: use a separate data structure for rx buffers
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>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
| H A D | init.c | diff 1a04d59d3ec982689552077172893b6836def984 Fri Oct 11 16:30:52 CDT 2013 Felix Fietkau <nbd@openwrt.org> ath9k: use a separate data structure for rx buffers
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>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
| H A D | ath9k.h | diff 1a04d59d3ec982689552077172893b6836def984 Fri Oct 11 16:30:52 CDT 2013 Felix Fietkau <nbd@openwrt.org> ath9k: use a separate data structure for rx buffers
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>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|