From owner-freebsd-net@FreeBSD.ORG Fri Sep 7 15:48:52 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 713A6106564A for ; Fri, 7 Sep 2012 15:48:52 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 40EDB8FC08 for ; Fri, 7 Sep 2012 15:48:52 +0000 (UTC) Received: from JRE-MBP-2.local (ppp121-45-230-94.lns20.per1.internode.on.net [121.45.230.94]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id q87Fmgp1086631 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 7 Sep 2012 08:48:44 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <504A1755.6090902@freebsd.org> Date: Fri, 07 Sep 2012 23:48:37 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: Anuranjan Shukla References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" Subject: Re: Proposal for changes to network device drivers and network stack (RFC) 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: Fri, 07 Sep 2012 15:48:52 -0000 On 9/7/12 4:28 PM, Anuranjan Shukla wrote: > Hi George, > Thanks for taking a look. Some answers/comments below. > >>> Building FreeBSD without the network stack (network stack as a module) >>> ---------------------------------------------------------------------- >>> >> This would be interesting for many reasons, and I think it would be a good >> contribution. Does the work you've done in this area handle the VNET >> stuff that is in the stack as well? That is, how well does the network >> stack >> as a module play with the vnet architecture? > I'll follow up on this one separately. > >>> struct socket { >>> >>> int so_fibnum; /* routing domain for this socket */ >>> uint32_t so_user_cookie; >>> + u_int so_oqueue; /* manage send prioritizing based on >>> application >>> needs */ >>> + u_short so_lrid; /* logical routing */ >>> }; >>> >> I'd be interested to know how this is used. > We use the first one as a 'direction' to the forwarding path to select an > appropriate priority queue to send the packet on. In a generic (i.e. > Something other than our specific system) system, one could consider > interesting ways to use queues on a multi queue NIC with help from a > driver. The second one is for a system with logical routing capabilities > (multiple routing systems within the same chassis). It gives an > application opening a socket an option to select the specific logical > routing instance. We have the second one with the SETFIB socket option, which allows a socket to select the routing instance (fib) to use. it's in the diff, 3 lines up. > I'll provide smaller pieces of diffs for the kernel without networking > patch I'd sent out. Let me know if you prefer the device driver interface > to be in that too. > > Thanks, > Anu > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > >