Date: Mon, 03 Jun 2013 14:06:57 -0700 From: Colin Percival <cperciva@freebsd.org> To: Andre Oppermann <andre@FreeBSD.org> Cc: freebsd-xen@FreeBSD.org Subject: Re: svn commit: r251297 - head/sys/dev/xen/netfront Message-ID: <51AD0571.90007@freebsd.org> In-Reply-To: <201306031300.r53D0XUx092178@svn.freebsd.org> References: <201306031300.r53D0XUx092178@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/03/13 06:00, Andre Oppermann wrote: > Log: > Specify a maximum TSO length limiting the segment chain to what the > Xen host side can handle after defragmentation. > > This prevents the driver from throwing away too long TSO chains and > improves the performance on Amazon AWS instances with 10GigE virtual > interfaces to the normally expected throughput. Thanks! For the benefit of the list: This (and the r251296, which provides the network stack infrastructure which this commit uses) was the last of the "make FreeBSD behave well in Amazon EC2" patches I've been carrying around (and building into my EC2 images) for the past two years. Now the only step remaining to make FreeBSD/EC2 pure "straight off the RELEASE ISO" FreeBSD is to get Xen HVM functionality into GENERIC. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51AD0571.90007>