From owner-freebsd-net@FreeBSD.ORG  Thu Feb 13 18:38:24 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 7C269BB2
 for <freebsd-net@freebsd.org>; Thu, 13 Feb 2014 18:38:24 +0000 (UTC)
Received: from hergotha.csail.mit.edu
 (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1CC74135D
 for <freebsd-net@freebsd.org>; Thu, 13 Feb 2014 18:38:24 +0000 (UTC)
Received: from hergotha.csail.mit.edu (localhost [127.0.0.1])
 by hergotha.csail.mit.edu (8.14.7/8.14.7) with ESMTP id s1DIcMRs047897;
 Thu, 13 Feb 2014 13:38:22 -0500 (EST)
 (envelope-from wollman@hergotha.csail.mit.edu)
Received: (from wollman@localhost)
 by hergotha.csail.mit.edu (8.14.7/8.14.4/Submit) id s1DIcM8i047896;
 Thu, 13 Feb 2014 13:38:22 -0500 (EST) (envelope-from wollman)
Date: Thu, 13 Feb 2014 13:38:22 -0500 (EST)
Message-Id: <201402131838.s1DIcM8i047896@hergotha.csail.mit.edu>
From: wollman@bimajority.org
To: scott4long@yahoo.com
Subject: Re: Use of contiguous physical memory in cxgbe driver
X-Newsgroups: mit.lcs.mail.freebsd-net
In-Reply-To: <5CAE71A4-EA1D-481D-AFBA-3738F8E66087@yahoo.com>
References: <21216.22944.314697.179039@hergotha.csail.mit.edu>
 <201402111348.52135.jhb@freebsd.org>
 <CAJ-VmonCdNQPUCQwm0OhqQ3Kt_7x6-g-JwGVZQfzWTgrDYfmqw@mail.gmail.com>
 <201402121446.19278.jhb@freebsd.org>
 <21244.20212.423983.960018@hergotha.csail.mit.edu>
 <20140213075651.GY34851@funkthat.com>
 <21245.1163.754141.154430@hergotha.csail.mit.edu>
Organization: none
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (hergotha.csail.mit.edu [127.0.0.1]); Thu, 13 Feb 2014 13:38:22 -0500 (EST)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED
 autolearn=disabled version=3.3.2
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
 hergotha.csail.mit.edu
Cc: freebsd-net@freebsd.org
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 18:38:24 -0000

In article <5CAE71A4-EA1D-481D-AFBA-3738F8E66087@yahoo.com>, Scott
Long writes:

>So what you’re saying is that all of the other memory allocations that
>go along with
>moving data through a socket wind up fragmenting the free memory pool to
>the point
>where it becomes impossible to find 3 contig pages for a 9k jumbo RX frame.

Yes.  I don't think it's even all that difficult, because drivers that
are of this type only ever allocate 9k clusters, and for outbound
packets the kernel never allocates anyting bigger than a page.  Since
the NIC driver allocates a new mbuf immediately to replenish its rx
ring, before the upper layers have had a chance to process the packet,
it's not hard to see how even a moderately busy system will soon
checkerboard all of physical memory.

-GAWollman