Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 May 2007 17:17:15 -0700
From:      Julian Elischer <julian@elischer.org>
To:        Andrew Thompson <thompsa@FreeBSD.org>
Cc:        freebsd-net <freebsd-net@freebsd.org>, Jack Vogel <jfvogel@gmail.com>
Subject:   Re: driver packet coalesce
Message-ID:  <465E140B.2080007@elischer.org>
In-Reply-To: <20070530235456.GA67464@heff.fud.org.nz>
References:  <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> <20070530235456.GA67464@heff.fud.org.nz>

next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Thompson wrote:
> On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote:
>> Does any driver do this now? And if a driver were to coalesce
>> packets and send something up the stack that violates mss
>> will it barf?
> 
> It would barf for things like bridging where the packet gets spit out a
> different interface. The bridge driver already has code to disable
> txcsum so it could be made to handle that too.
> 
> 
> Andrew
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

This is part od TOE right?

I presume that it wouldn't coalesce packets that are not destined for the local
machine?  would it coalesce in promiscuous mode?   I guess it would only be 
able to coalesce TCP packets that are adjacent in the same session. 
Whether it also can coalesce adjacent packets that are destined for another
machine (for which it is not running the session) is not known... I would guess it
wouldn't do it.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465E140B.2080007>