Date: Mon, 11 Mar 2013 09:38:12 -0700 From: Jack Vogel <jfvogel@gmail.com> To: Garrett Wollman <wollman@hergotha.csail.mit.edu> Cc: freebsd-net@freebsd.org, rmacklem@uoguelph.ca, andre@freebsd.org Subject: Re: Limits on jumbo mbuf cluster allocation Message-ID: <CAFOYbck-m%2B71Ma7w2ixQNrFfN55pe6SOtGkNzm1AtahQe5S-FA@mail.gmail.com> In-Reply-To: <201303111605.r2BG5I6v073052@hergotha.csail.mit.edu> References: <1154859394.3748712.1362959165419.JavaMail.root@erie.cs.uoguelph.ca> <513DB550.5010004@freebsd.org> <201303111605.r2BG5I6v073052@hergotha.csail.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
How large are you configuring your rings Garrett? Maybe if you tried reducing them? Jack On Mon, Mar 11, 2013 at 9:05 AM, Garrett Wollman < wollman@hergotha.csail.mit.edu> wrote: > In article <513DB550.5010004@freebsd.org>, andre@freebsd.org writes: > > >Garrett's problem is receive side specific and NFS can't do much about it. > >Unless, of course, NFS is holding on to received mbufs for a longer time. > > Well, I have two problems: one is running out of mbufs (caused, we > think, by ixgbe requiring 9k clusters when it doesn't actually need > them), and one is livelock. Allowing potentially hundreds of clients > to queue 2 MB of requests before TCP pushes back on them helps to > sustain the livelock once it gets started, and of course those packets > will be of the 9k jumbo variety, which makes the first problem worse > as well. > > -GAWollman > > _______________________________________________ > 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFOYbck-m%2B71Ma7w2ixQNrFfN55pe6SOtGkNzm1AtahQe5S-FA>