yes. Microblaze is very sensitive on it. I have spent a couple of days
to find out why bandwidth is so bad and I found that truesize is the
problem. Whole driver allocated skb buffer to max mtu size (9000).
But if mtu is 1500 the driver still worked with max skb buffers size
Please correct me if I am wrong but if truesize is setup to 9000 then
net code is working with that size even if mtu is 1500.
The next thing is that cache operations take a lot of cpu cycles.
I create a patch which allocated aligned skb buffers where size depends
on current mtu size and this change rapidly increase bandwidth for
mtu=1500 from 8Mb/s to 35Mb/s (depends on setting). There is no
difference if jumbo frames are used (I means for driver with/without my
patch).
I am using non-mainline ll_temac driver.
drivers/net/xilinx_lltemac/
http://developer.petalogix.com/git/gitweb.cgi?p=linux-2.6-microblaze.git;a=shortlog
Regards,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html