public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Andrew Morton <akpm@osdl.org>
Cc: manfred@colorfullife.com, linux-kernel@vger.kernel.org,
	Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: [PATCH] Allow TSO to be disabled for forcedeth driver
Date: Thu, 01 Jun 2006 13:07:09 -0700	[thread overview]
Message-ID: <447F48ED.6090202@vmware.com> (raw)
In-Reply-To: <20060601125359.10ca1f2b.akpm@osdl.org>

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

  reply	other threads:[~2006-06-01 20:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 19:27 [PATCH] Allow TSO to be disabled for forcedeth driver Zachary Amsden
2006-06-01 19:53 ` Andrew Morton
2006-06-01 20:07   ` Zachary Amsden [this message]
     [not found] <DBFABB80F7FD3143A911F9E6CFD477B00BA5E36B@hqemmail02.nvidia.com>
     [not found] ` <20060601142909.369cf12f.akpm@osdl.org>
     [not found]   ` <447F6E13.8030904@vmware.com>
     [not found]     ` <447F472E.5060808@nvidia.com>
2006-06-02  5:49       ` Zachary Amsden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=447F48ED.6090202@vmware.com \
    --to=zach@vmware.com \
    --cc=aabdulla@nvidia.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox