From owner-freebsd-net@FreeBSD.ORG Sat Sep 25 07:30:02 2010 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B59CC106566C for ; Sat, 25 Sep 2010 07:30:02 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from out-0.mx.aerioconnect.net (out-0-27.mx.aerioconnect.net [216.240.47.87]) by mx1.freebsd.org (Postfix) with ESMTP id 9796B8FC13 for ; Sat, 25 Sep 2010 07:30:02 +0000 (UTC) Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160]) by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id o8P7Ib5p002537 for ; Sat, 25 Sep 2010 00:18:37 -0700 X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id 4C88D2D601A for ; Sat, 25 Sep 2010 00:18:36 -0700 (PDT) Message-ID: <4C9DA26D.7000309@freebsd.org> Date: Sat, 25 Sep 2010 00:19:09 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51 Cc: Subject: mbuf changes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2010 07:30:02 -0000 over the last few years there has been a bit of talk about some changes people want to see in mbufs for 9.x extra fields, changes in the way things are done, etc. If you are one of these people, pipe up now.. to get the ball rolling.. * Add a field for the current FIB.. currently this is 4 bits stolen from the flags. what would be a good width: 8,12,16,24,32 bits? this would allow setfib to use numbers greater than 16 (the current max) * Preallocating some room for some number of tags before we start allocating (expensively) new ones. * dynamically working out what the front padding size should be.. per session.. i.e. when a packet is sent out and needs to be adjusted to add more headers, the originating socket should be notified, or maybe the route should have this information... so that future packets can start out with enough head room. (this is not strictly to do with mbufs but might need some added field to point to the structure that needs to be updated. I'm sure some of our luminaries have ideas.. Speak up! also, while I'm here will the person who made the patches to allow ifconfig(8) to set a default fib on an interface please stand up? julian