From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 18 00:03:10 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 456A5AEB for ; Sun, 18 Nov 2012 00:03:10 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (gribble.egr.msu.edu [35.9.37.169]) by mx1.freebsd.org (Postfix) with ESMTP id 157118FC08 for ; Sun, 18 Nov 2012 00:03:09 +0000 (UTC) Received: from gribble (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 5C3C573699; Sat, 17 Nov 2012 18:53:58 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by gribble (gribble.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fk06nD08gfUg; Sat, 17 Nov 2012 18:53:58 -0500 (EST) Received: from EGR authenticated sender Message-ID: <50A8239D.3080008@egr.msu.edu> Date: Sat, 17 Nov 2012 18:54:05 -0500 From: Adam McDougall User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Zaphod Beeblebrox , hackers@freebsd.org Subject: Re: Jumbo Packet fail. References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 18 Nov 2012 01:57:04 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 00:03:10 -0000 On 11/17/2012 5:32 PM, Zaphod Beeblebrox wrote: > I recently started using an iSCSI disk on my ZFS array seriously from > a windows 7 host on the network. The performance is acceptable, but I > was led to believe that using Jumbo packets is a win here. My win7 > motherboard adapter did not support jumbo frames, so I got one that > did... configured it, etc. Just in case anyone cares, the motherboard > had an 82567V-2 (does not support jumbo frames) and I added in an > intel 82574L based card. > > Similarly, I configured em0 on my FreeBSD host to have an MTU of 9014 > bytes (I also tried 9000). The hardware on the FreeBSD 9.1RC2 side > is: > > em0: port 0xdc00-0xdc1f > mem 0xfcfe0000-0xfcffffff,0xfcfc0000-0xfcfdffff irq 16 at device 0.0 > on pci3 > > pciconf -lv identifies the chipset as 82572EI > > Now... my problem is that the windows machine correctly advertises an > MSS of 8960 bytes in it's SYN packet while FreeBSD advertises 1460 in > the syn-ack. > > [1:42:342]root@vr:/usr/local/etc/istgt> ifconfig em0 > em0: flags=8843 metric 0 mtu 9014 > options=4019b > ether 00:15:17:0d:04:a8 > inet 66.96.20.52 netmask 0xffffffe0 broadcast 66.96.20.63 > inet6 fe80::215:17ff:fe0d:4a8%em0 prefixlen 64 scopeid 0x5 > inet6 2001:1928:1::52 prefixlen 64 > inet 192.168.221.2 netmask 0xffffff00 broadcast 192.168.221.255 > nd6 options=21 > media: Ethernet autoselect (1000baseT ) > status: active > > I have tested this with both ipv4 and ipv6 connections between the > win7 host and the FreeBSD server. win7 always requests the larger > mss, and FreeBSD the smaller. Did you reboot or alter the existing route so it also uses the higher MTU? I realize that need is not obvious. Check netstat -rni.