From owner-freebsd-xen@FreeBSD.ORG Wed Nov 3 22:37:08 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 783D21065679 for ; Wed, 3 Nov 2010 22:37:08 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 0C48D8FC1A for ; Wed, 3 Nov 2010 22:37:07 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id oA3MBmoD020299; Wed, 3 Nov 2010 16:11:48 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id oA3MBm2F020298; Wed, 3 Nov 2010 16:11:48 -0600 (MDT) (envelope-from ken) Date: Wed, 3 Nov 2010 16:11:48 -0600 From: "Kenneth D. Merry" To: Yuriy Kohut Message-ID: <20101103221148.GA17412@nargothrond.kdm.org> References: <88955623-5D2F-453A-B7EF-9E1058370B14@onapp.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <88955623-5D2F-453A-B7EF-9E1058370B14@onapp.com> User-Agent: Mutt/1.4.2i Cc: "freebsd-xen@FreeBSD.org" Subject: Re: FreeBSD 8.1-RELEASE-p1 i386 xennet_get_responses messages in console X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2010 22:37:08 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Oct 28, 2010 at 15:02:41 +0300, Yuriy Kohut wrote: > Hi, > > Does somebody know haw to deal with the following massages in the console: > > xennet_get_responses: too many frags 6 > max 5 What are you using for your Domain 0? I haven't run into that before, so it would be nice to have a setup that would trigger this problem. It looks like there is a limit on the number of segments for LRO. I think the limit is arbitrary, but I need to look at it a bit more. Try the attached patch and let me know whether it works for you. It disables the limit on the number of receive segments. Thanks, Ken -- Kenneth Merry ken@FreeBSD.ORG --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="netfront.c.rx_max.stable.20101103.txt" ==== //depot/SpectraBSD/stable/8/sys/dev/xen/netfront/netfront.c#2 - /usr/home/kenm/perforce4/SpectraBSD/stable/8/sys/dev/xen/netfront/netfront.c ==== *** /tmp/tmp.3226.94 Wed Nov 3 16:09:10 2010 --- /usr/home/kenm/perforce4/SpectraBSD/stable/8/sys/dev/xen/netfront/netfront.c Wed Nov 3 16:08:35 2010 *************** *** 1272,1278 **** --- 1272,1280 ---- struct mbuf *m, *m0, *m_prev; grant_ref_t ref = xennet_get_rx_ref(np, *cons); RING_IDX ref_cons = *cons; + #if 0 int max = 5 /* MAX_TX_REQ_FRAGS + (rx->status <= RX_COPY_THRESHOLD) */; + #endif int frags = 1; int err = 0; u_long ret; *************** *** 1416,1421 **** --- 1418,1424 ---- } *list = m0; + #if 0 if (unlikely(frags > max)) { if (net_ratelimit()) WPRINTK("Too many frags\n"); *************** *** 1423,1428 **** --- 1426,1432 ---- max); err = E2BIG; } + #endif *cons += frags; --azLHFNyN32YCQGCU--