Keval_Joshi

Hello rgrr, The same thing has been observed on my platform. RNDIS performance is fairly reasonable, But NCM is 10 times slower then RNDIS. My Prime suspect is the way...

> Hmmm, does anybody read this? > > I want to make a proposal: the ncm_device driver seems to be very buggy, e.g. it operates on incoming frames while the...

Hello rgrr, Thanks for finding out these bugs I'll test this on my device and let you know.

> Hmmm, does anybody read this? > > I want to make a proposal: the ncm_device driver seems to be very buggy, e.g. it operates on incoming frames while the...

rgrr, Kudos and thanks for writing a very clear concise documentation. I was able to see that the NCM bandwidth increased by a factor or 2 :smile: . However I...

Yup I am using standard lwip webserver example from TinyUSB and iperf application from lwip-contrib/examples/lwiperf I am executing following command. for MSS in 100 200 400 800 1200 1450 1500;...

rgrr, I have confirmed that , lwip-webserver is also running fine on my platform. >> "WARNING: attempt to set TCP maximum segment size to 100, but got 536". That also...

I have taken a reference of glue logic from https://github.com/rgrr/yapicoprobe/blob/feature/minor-cleanup/src/net/net_glue.c Implemented the same. As I increased the TinyUSB buffer size, the test case worked for all segment size. :smiley: iperf...

>> Actually I have no idea what the bottleneck could be. Have you checked the wireshark log if you see the expected? Perhaps your iperf behaves not as you want....