Date: Fri, 12 Nov 2004 13:20:50 -0800
From: "David S. Miller" <davem@davemloft.net>
To: "Godse, Radheka" <radheka.godse@intel.com>
Cc: bonding-devel@lists.sourceforge.net, fubar@us.ibm.com,
       ctindel@users.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Bonding-devel][PATCH]Zero Copy Transmit Support (Update)
Message-Id: <20041112132050.45b83434.davem@davemloft.net>
In-Reply-To: <F760B14C9561B941B89469F59BA3A8470823F9A6@orsmsx401.amr.corp.intel.com>
References: <F760B14C9561B941B89469F59BA3A8470823F9A6@orsmsx401.amr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 755
Lines: 19

On Fri, 12 Nov 2004 13:31:53 -0800
"Godse, Radheka" <radheka.godse@intel.com> wrote:

> I had similar thoughts but then, the bond device does not have any
> slaves attached to it at load time. By publishing them upfront the bond
> device is able to take advantage of hardware acceleration if it is later
> available...

This is not a problem at all.

You can make ethtool calls on the bonding device to change
settings later.  Nothing prevents you from changing the
SG/CSUM/TSO bits after device registration.

-
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/