From owner-freebsd-chat@FreeBSD.ORG Wed Oct 15 17:34:54 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AED616A4B3 for ; Wed, 15 Oct 2003 17:34:54 -0700 (PDT) Received: from pixies.tirloni.org (pixies.tirloni.org [200.203.183.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06FE143FA3 for ; Wed, 15 Oct 2003 17:34:54 -0700 (PDT) (envelope-from tirloni@tirloni.org) Received: by pixies.tirloni.org (Postfix, from userid 1000) id EE8EE1E1426; Wed, 15 Oct 2003 22:34:52 -0200 (BRST) Date: Wed, 15 Oct 2003 22:34:52 -0200 From: "Giovanni P. Tirloni" To: freebsd-chat@freebsd.org Message-ID: <20031016003452.GJ89469@pixies.tirloni.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: Network stack presentation - community input needed X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 00:34:54 -0000 Hi, I'm preparing a slide presentation about our network stack. It's targeted at the averate/intermediate network administrator that usually deals with NAT, filtering, bridging, IPSec, etc. I'd like input from the community, if possible, about what's a good way to present this beast. I've two ideas, 1) Show the features and numbers - A bit of history - What is supported - Performance numbers - Where it can be used - Small overview of each feature 2) How it's designed - No history - What are the big players (mbufs, interrupts, priorities, queues) - Where is possible to tweak it and how - The big picture - How packets travel (receive, send, forward, bridge, filter) - Where features (bridge, pfil/ipfw, netgraph) happen (above) I guess I would have to spend more time explaining mbufs, interrupts, priorities and other basic kernel components. Would that be excessive? If I choose the second path what are the most important things one should know when designing for performance and security? Anything to add to the list I made? I think I'm too focused on mbufs, interrupts and queues (ip input, socket buffers, iface output), anything else? I would like it to be a starting point for people interested in going deeper in the details. I should take about 45 minutes. Thanks in advance, -- Giovanni P. Tirloni Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26