From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 11 23:35:16 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D282112F for ; Tue, 11 Feb 2014 23:35:16 +0000 (UTC) Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8C10E1024 for ; Tue, 11 Feb 2014 23:35:16 +0000 (UTC) Received: by mail-ve0-f177.google.com with SMTP id jz11so6646447veb.36 for ; Tue, 11 Feb 2014 15:35:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=0ISVvZc33YD3mAGBtafLJSHeaL/aDv+SpLdlUSOCWo0=; b=QBJFY+wO3lV3kDbno4bdmQ/OD7qk+IuAUuIPdNwotj9VUwyr8zrkHRi0gsFNefSnqt xfqW6AU2p/UHf8RItP33WGRayTvGG/8sEtLTrtgo/z6i5ni/pmoHwJftLIeqjJSXeAxq K5EAvQnYIboZ1uCu/y9U0l7w+rTcekcdP2BqeSiVkjMa2JfYfulrOY+gu0ggzn/FsPWB KJRR7rT4YuF2+Bc59UjAi7Jq2EAZEIRsu0fmG72h48x8/kFKcNdkEJ4axQw6L4DLtVXC QmvkkCCxgzVsaCQBjDF1NeGxQbSdtNFLERQjONA3jEhWMY2grIcS5gBQbBKYZOkeMfH9 vpBw== MIME-Version: 1.0 X-Received: by 10.52.236.132 with SMTP id uu4mr47231vdc.47.1392161715632; Tue, 11 Feb 2014 15:35:15 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.220.113.199 with HTTP; Tue, 11 Feb 2014 15:35:15 -0800 (PST) In-Reply-To: <1AECA876-08BC-48F8-B356-42CE35100805@ramattack.net> References: <1AECA876-08BC-48F8-B356-42CE35100805@ramattack.net> Date: Tue, 11 Feb 2014 15:35:15 -0800 X-Google-Sender-Auth: uPBrUYBZ0YyeOLrHHZzW-sU7lTw Message-ID: Subject: Re: mbuf_tag memory freeing issues with LRO enabled on the XENHVM driver From: Adrian Chadd To: Egoitz Aurrekoetxea Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2014 23:35:16 -0000 +net .. any ideas? -a On 11 February 2014 10:05, Egoitz Aurrekoetxea wrote: > Good afternoon, > > It seems the LRO code inside the FreeBSD's kernel is causing the first mbuf chain's anymbuf->m_hdr->mh_flags due to some failure not to contain the M_PKTHDR flag. > Have you ever seen this bad behavior with any of these drivers having LRO enabled : > > cxgb > cxgbe > e1000 > ixgbe > ixgbe > mxge > oce > qlxgb > qlxge > virtio > vxge > > The no presence of this flag, seems to be causing the kernel not to be able to enter : > > static void > mb_dtor_pack(void *mem, int size, void *arg) > { > struct mbuf *m; > > m = (struct mbuf *)mem; > if ((m->m_flags & M_PKTHDR) != 0) > m_tag_delete_chain(m, NULL); <============ to this function. > > causing the wired memory to increase a lot due mbuf_tags usage memory to be pretty high. > > I have noticed about this issue using the XENHVM network driver (xn), but taking a look at some other drivers using the same code as this one... have found the commented before ones.... > > Has anyone too suffered the issue?. > > Best regards, > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"