Re: driver packet coalesce
- From: "Bruce M. Simpson" <bms@xxxxxxxxxxx>
- Date: Thu, 31 May 2007 19:29:06 +0100
Jack Vogel wrote:
On 5/31/07, Wilkinson, Alex <alex.wilkinson@xxxxxxxxxxxxxxxxxxx> wrote:0n Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote:combining packets before sending to the stack, aka LRO.
> 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?
erm, what is meant by "coalesce" ?
Yup - the firmware for the card's LRO engine would have to know not to coalesce packets not destined for the local host. I speculate many cards are not smart enough to do this, and LRO is an all-or-nothing proposition, as it's a technology designed to optimize for hosts, not routers; see recent discussions/slanging matches on end2end.
At the moment there is no central place where we track all layer 2 addresses for which traffic should be delivered locally. This would logically belong in struct ifnet, and clients e.g. CARP would have to be taught to add their layer 2 endpoint addresses there.
It seems acceptable to disable LRO if bridging is on and document this behaviour.
BMS
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: driver packet coalesce
- From: Kip Macy
- Re: driver packet coalesce
- References:
- driver packet coalesce
- From: Jack Vogel
- Re: driver packet coalesce
- From: Wilkinson, Alex
- Re: driver packet coalesce
- From: Jack Vogel
- driver packet coalesce
- Prev by Date: Re: Download speed and TCPIP window sizing
- Next by Date: Re: New driver coming soon.
- Previous by thread: Re: driver packet coalesce
- Next by thread: Re: driver packet coalesce
- Index(es):
Relevant Pages
|
