From owner-freebsd-net@FreeBSD.ORG  Fri Mar  8 20:33:11 2013
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 6FC7AD6;
 Fri,  8 Mar 2013 20:33:11 +0000 (UTC)
 (envelope-from jfvogel@gmail.com)
Received: from mail-vb0-x22b.google.com (mail-vb0-x22b.google.com
 [IPv6:2607:f8b0:400c:c02::22b])
 by mx1.freebsd.org (Postfix) with ESMTP id 166C090C;
 Fri,  8 Mar 2013 20:33:11 +0000 (UTC)
Received: by mail-vb0-f43.google.com with SMTP id fs19so818997vbb.30
 for <multiple recipients>; Fri, 08 Mar 2013 12:33:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:in-reply-to:references:date:message-id
 :subject:from:to:cc:content-type;
 bh=/iBg7AYMgRUajUfsdvZt+hW9WgMVNk0duoiVzI09uNY=;
 b=FscbCUFsB28Z6Q/CpT5RGNkHo3ZQY/PQtVk4uOBx3SG8nZWReOvpsGAfhVeRX/czH6
 qAssvofTgp4S6rr6yD4uTka81b2gzVfRxEdazuXqOHWVdVJ5cxwakOshNdmIUnJNt2uh
 hYLIGRjGKVT8R2tumDR5FqmxI0FGdGMl6fga2t3kC+T/66w8kTfvqPNpE6nAUkGSlyQA
 v7Now3ABgoPQP6mfjRLlljxM2U1HgvZc5cNKVxM29rdBX0uDDNRwXe40Dq2I8syoG8Fj
 XXwYnMp9qnl6xHqmzaJURwOR7j+KdyxQ4Xzm/Ga5GxMOYoBW6mxBZhoT4/xRo4ccuhz9
 KbnQ==
MIME-Version: 1.0
X-Received: by 10.52.19.239 with SMTP id i15mr1317983vde.47.1362774789931;
 Fri, 08 Mar 2013 12:33:09 -0800 (PST)
Received: by 10.220.191.132 with HTTP; Fri, 8 Mar 2013 12:33:09 -0800 (PST)
In-Reply-To: <20794.18907.530374.164737@hergotha.csail.mit.edu>
References: <20793.36593.774795.720959@hergotha.csail.mit.edu>
 <51399926.6020201@freebsd.org>
 <CAFOYbc=x7U-s70KvcZJdrVP6v-On716qMi=HN1P2Kj+d_K972A@mail.gmail.com>
 <20794.6692.191898.682241@hergotha.csail.mit.edu>
 <513A2887.2010408@freebsd.org>
 <CAFOYbc=7iROKzUwnB0fMR=ix8VFo+ONfG=NX43jeF7jkp74JhQ@mail.gmail.com>
 <20794.18907.530374.164737@hergotha.csail.mit.edu>
Date: Fri, 8 Mar 2013 12:33:09 -0800
Message-ID: <CAFOYbcnHy+Oh2kjYTG7zj=te2Wi4A6vAOZKmYttMt12EoeW=WQ@mail.gmail.com>
Subject: Re: UNS: Re: Limits on jumbo mbuf cluster allocation
From: Jack Vogel <jfvogel@gmail.com>
To: Garrett Wollman <wollman@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: freebsd-net@freebsd.org
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.14
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: Fri, 08 Mar 2013 20:33:11 -0000

Yes, the write-back descriptor has a bit in the status field that says its
EOP (end of packet)
or not.

Jack


On Fri, Mar 8, 2013 at 12:28 PM, Garrett Wollman <wollman@freebsd.org>wrote:

> <<On Fri, 8 Mar 2013 12:13:28 -0800, Jack Vogel <jfvogel@gmail.com> said:
>
> > Yes, in the past the code was in this form, it should work fine Garrett,
> > just make sure
> > the 4K pool is large enough.
>
> I take it then that the hardware works in the traditional way, and
> just keeps on using buffers until the packet is completely written,
> then sets a field on the ring descriptor saying "the end of the packet
> is HERE"?
>
> I'll give that change a try when I get a chance.
>
> -GAWollman
>
>