From owner-freebsd-current@freebsd.org  Mon Jul 27 14:54:26 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C9399AC3E4
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 27 Jul 2015 14:54:26 +0000 (UTC)
 (envelope-from woodsb02@gmail.com)
Received: from mail-vn0-x235.google.com (mail-vn0-x235.google.com
 [IPv6:2607:f8b0:400c:c0f::235])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id E7EFDC7B;
 Mon, 27 Jul 2015 14:54:25 +0000 (UTC)
 (envelope-from woodsb02@gmail.com)
Received: by vnds125 with SMTP id s125so31665681vnd.1;
 Mon, 27 Jul 2015 07:54:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=5HJpq/63B38fgKWFlZxpcicq7LZwQlu8Isn7XVfKzps=;
 b=dlSXqLNJLU+zKhA+O77jQJZN+AJqkpH/D2MHKgokZty8uKmQByYWIB7s1wA9ZE2KHs
 rPqFx9FC1kESKHuWUHtsf1+VJgkVlzmh1kgZMQIpOROPo8igmryFpaCnwTNLlULsiFW8
 Ys/07a9M6nvZPaa0HLcyprmu+N5GrrAW9dCc5mtKeqSz/sWTxx4f6wW4xmmRtx1dMdU0
 8/eTCFdOLXC+KIh95KtbGKRKWCBybnFh+1r+t54A1h04jWb2Qa1CBaWA3QwMqAyQHagc
 xiHr/ioQMj6/cNJhPXruw6Bg3XT2j/iu9UqOOBgLz6O1ITRrn9cjjcqp98vx6axGRx4R
 JiAg==
MIME-Version: 1.0
X-Received: by 10.52.117.114 with SMTP id kd18mr34836797vdb.22.1438008864483; 
 Mon, 27 Jul 2015 07:54:24 -0700 (PDT)
Received: by 10.31.1.6 with HTTP; Mon, 27 Jul 2015 07:54:24 -0700 (PDT)
In-Reply-To: <55B60FC8.2020003@selasky.org>
References: <55B60FC8.2020003@selasky.org>
Date: Mon, 27 Jul 2015 22:54:24 +0800
Message-ID: <CAOc73CDu=ayPQcYti_F2GP53oD+sNUP78+SzzetgLE-LZ9-1aA@mail.gmail.com>
Subject: Re: E1000 mbuf leaks
From: Ben Woods <woodsb02@gmail.com>
To: Hans Petter Selasky <hps@selasky.org>
Cc: FreeBSD Current <freebsd-current@freebsd.org>,
 Sean Bruno <sbruno@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2015 14:54:26 -0000

On Monday, July 27, 2015, Hans Petter Selasky <hps@selasky.org> wrote:

> Hi,
>
> I'm currently doing some busdma work, and possibly stepped over some
> driver bugs. When "bus_dmamap_load_mbuf_sg()" returns ENOMEM the mbuf chain
> is not freed. Is there some magic in "bus_dmamap_load_mbuf_sg()" for that
> error code or is there a possible memory leak in all E1000 drivers? See
> attached patch.


Would this explain the high mbuf usage seen on pfsense when using the
igb(4) or em(4) Intel NIC drivers?


https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#Intel_igb.284.29_and_em.284.29_Cards

Regards,
Ben


-- 

--
From: Benjamin Woods
woodsb02@gmail.com