lkml.org 
[lkml]   [2006]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
DateThu, 01 Jun 2006 13:07:09 -0700
FromZachary Amsden <>
SubjectRe: [PATCH] Allow TSO to be disabled for forcedeth driver
Andrew Morton wrote:
> Zachary Amsden <zach@vmware.com> wrote:
>
>> TSO can cause performance problems in certain environments, and being
>> able to turn it on or off is helpful for debugging network issues. Most
>> other network drivers that support TSO allow it to be toggled, so add
>> this feature to forcedeth. Tested by Harald Dunkel, who reported that
>> this fixed his network performance issue with VMware.
>>
>>
>
> (This is regarding
> http://www.vmware.com/community/thread.jspa?messageID=408893)
>
>
> Why does TSO-with-forcedeth make vmware networking slow?
>
> Is it specific to the forcedeth driver?
>

No. TSO is not good for bridged virtual networking in general, since
even if the bridged networking module understood TSO, it would then have
to split up any large packets into smaller packets to pass on to the
guest virtual machine - or require that the guest virtual machine have
and understand how to use a TSO compatible network interface as well.
Both solutions are extremely problematic, and the easiest thing to do is
just disable TSO. It makes sense for any protocol bridge device,
including some firewall configurations.

Zach
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-06-01 22:09    [from the cache]
©2003-2010