Felix Fietkau 0c285bd081 ramips: ethernet: use own page_frag_cache ... Using the NAPI or netdev frag cache along with other drivers can lead to 32 KiB pages being held for a long time, despite only being used for very few page fragment. This can happen if the ethernet driver grabs one or two fragments for rx ring refill, while other drivers use (and free up) the remaining fragments. The 32 KiB higher-order page can only be freed once all users have freed their fragments, which only happens after the rings of all drivers holding the fragments have wrapped around. Depending on the traffic patterns, this can waste a lot of memory and look a lot like a memory leak Signed-off-by: Felix Fietkau <nbd@nbd.name>		2018-07-12 18:43:53 +02:00
..
esw_rt3050.c
esw_rt3050.h
ethtool.c
ethtool.h
gsw_mt7620.c
gsw_mt7620.h
gsw_mt7621.c
Kconfig
Makefile
mdio_mt7620.c
mdio_rt2880.c
mdio_rt2880.h
mdio.c
mdio.h
mt7530.c
mt7530.h
mtk_debugfs.c
mtk_eth_soc.c	ramips: ethernet: use own page_frag_cache	2018-07-12 18:43:53 +02:00
mtk_eth_soc.h	ramips: ethernet: use own page_frag_cache	2018-07-12 18:43:53 +02:00
mtk_offload.c
mtk_offload.h
soc_mt7620.c
soc_mt7621.c	ramips: improve ethernet driver performance with GRO/TSO	2018-06-19 09:45:28 +02:00
soc_rt2880.c
soc_rt3050.c
soc_rt3883.c