On 6/26/11, Geoff Galitz <geoff@xxxxxxxxxx> wrote:
> In short, the entire path from origin to destination must be configured to
> support jumbo frames. If not, then the devices at various points in the
> path will attempt to scale and you'll end up getting fragmentation and
> higher overhead in the devices leading to worse overall performance.
>
> Have you verified this is the case?
I believed so everything along the path supports the MTU size I was
testing with. The test path is short, basically NIC -> Lan Cable -> HP
1910 -> Lan Cable -> NIC.
The switch is spec'd to support up to 9K jumbo frame, enabled by
default based on a FAQ I found on 3Com/HP when trying to figure out
where do I turn it on.
> Of course, the quality of the driver for your NIC will also play a role.
This I have no idea which was why I was wondering about the elrepo driver.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
