Date: Thu, 20 Mar 2014 17:13:07 -0400 (EDT) From: Garrett Wollman <wollman@hergotha.csail.mit.edu> To: csforgeron@gmail.com Cc: freebsd-net@freebsd.org Subject: Re: 9.2 ixgbe tx queue hang Message-ID: <201403202113.s2KLD7GB085085@hergotha.csail.mit.edu> In-Reply-To: <CAB2_NwAOmPtZjB03pdDiTK2OvQgqk-tYf83Jq4Ukt9jnZA8CNA@mail.gmail.com> References: <CAB2_NwDG=gB1WCJ7JKTHpkJCrvPuAhipkn%2BvPyT%2BxXzOBrTGkg@mail.gmail.com> <1159309884.25490921.1395282576806.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <CAB2_NwAOmPtZjB03pdDiTK2OvQgqk-tYf83Jq4Ukt9jnZA8CNA@mail.gmail.com>, csforgeron@gmail.com writes: >50/27433/0 requests for jumbo clusters denied (4k/9k/16k) This is going to screw you. You need to make sure that no NIC driver ever allocates 9k jumbo pages -- unless you are using one of those mythical drivers that can't do scatter/gather DMA on receive, which you don't appear to be. These failures occur when the driver is trying to replenish its receive queue, but is unable to allocate three *physically* contiguous pages of RAM to construct the 9k jumbo cluster (of which the remaining 3k is simply wasted). This happens on any moderately active server, once physical memory gets checkerboarded with active single pages, particularly with ZFS where those pages are wired in kernel memory and so can't be evicted. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403202113.s2KLD7GB085085>