Thanks. Enabling TSO can make the issue easily occur. Well, this is just a clue.
The back port is not done by me, and the people who did that because their system is based on 9.2, and it takes a lot of effort to upgrade FreeBSD system. -----Original Message----- From: Adrian Chadd [mailto:adrian.ch...@gmail.com] Sent: 2015年11月23日 23:31 To: Hongjiang Zhang <honz...@microsoft.com> Cc: freebsd-net@freebsd.org Subject: Re: Is it allowed to copy hyper-v drivers from FreeBSD 10 and packed it into FreeBSD 9.2 On 22 November 2015 at 21:58, Hongjiang Zhang <honz...@microsoft.com> wrote: > Hi, > > Some people, who used FreeBSD 9.2 and back-port network driver for Hyper-v > from FreeBSD 10, encountered a network issue. They installed 2 VM (FreeBSD > 9.2 with the customized FreeBSD kernel) on Azure. Network went offline very > soon when the big file (~320M byte) is copied from one VM to anther through > "scp". If TSO is disabled through "sysctl -w net.inet.tcp.tso=0", this issue > will be alleviated but cannot be eliminated. I did not figure out why. > > I have checked the release notes of FreeBSD 9.2/9.3/10, but did not find > anything which blocked the back-port. It is supposed 9.2 allows the > back-ported Hyper-v drivers from 10. Is this assumption correct? Hi! It may be something to do with maximum mbufs per packet or some other limit like that. Is there a lot of interest in backporting the latest hyperv driver to 9.2? -a > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2flists > .freebsd.org%2fmailman%2flistinfo%2ffreebsd-net&data=01%7c01%7chonzhan > %40064d.mgd.microsoft.com%7c1bc312a0449d4fb61bc708d2f41b07db%7c72f988b > f86f141af91ab2d7cd011db47%7c1&sdata=bNEhroIlwhoTHyG3bhHlQ2DYJY5FWMi8A1 > 23TVeZ7Dc%3d To unsubscribe, send any mail to > "freebsd-net-unsubscr...@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"