On 06/03/13 09:00, Andre Oppermann wrote:
Author: andre
Date: Mon Jun 3 13:00:33 2013
New Revision: 251297
URL: http://svnweb.freebsd.org/changeset/base/251297
Log:
Specify a maximum TSO length limiting the segment chain to what the
Xen host side can handle after defragmentation.
On 06/03/13 23:00, Andre Oppermann wrote:
Author: andre
Date: Mon Jun 3 13:00:33 2013
New Revision: 251297
URL: http://svnweb.freebsd.org/changeset/base/251297
Log:
Specify a maximum TSO length limiting the segment chain to what the
Xen host side can handle after defragmentation.
On 06/04/13 22:51, Lawrence Stewart wrote:
On 06/03/13 23:00, Andre Oppermann wrote:
Modified: head/sys/dev/xen/netfront/netfront.c
==
--- head/sys/dev/xen/netfront/netfront.c Mon Jun 3 12:55:13 2013
On 05.06.2013 08:13, Colin Percival wrote:
On 06/04/13 22:51, Lawrence Stewart wrote:
On 06/03/13 23:00, Andre Oppermann wrote:
Modified: head/sys/dev/xen/netfront/netfront.c
==
--- head/sys/dev/xen/netfront/netfront.c
On Tue, Jun 04, 2013 at 23:13:54 -0700, Colin Percival wrote:
On 06/04/13 22:51, Lawrence Stewart wrote:
On 06/03/13 23:00, Andre Oppermann wrote:
Modified: head/sys/dev/xen/netfront/netfront.c
==
---
On 4 June 2013 23:13, Colin Percival cperc...@freebsd.org wrote:
The comment above (of which only the last line is quoted in the diff)
explains it:
* This limit is imposed by the backend driver. We assume here that
* we are dealing with a Linux driver domain and have set our limit
* to
Author: andre
Date: Mon Jun 3 13:00:33 2013
New Revision: 251297
URL: http://svnweb.freebsd.org/changeset/base/251297
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
