On 23/11/2015 11:30 PM, Adrian Chadd wrote:
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?
I believe we ($JOB) have them back ported to 8.0. (I didn't do the work)
-a
_______________________________________________
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"
_______________________________________________
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"
_______________________________________________
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"
