From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 10 17:50:46 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7F54106566B for ; Mon, 10 Mar 2008 17:50:46 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.tele2.se [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id 143DF8FC1B for ; Mon, 10 Mar 2008 17:50:45 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [62.113.132.89] (account mc467741@c2i.net [62.113.132.89] verified) by mailfe12.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 671482948; Mon, 10 Mar 2008 17:50:41 +0100 From: Hans Petter Selasky To: Alexander Leidinger Date: Mon, 10 Mar 2008 17:51:46 +0100 User-Agent: KMail/1.9.7 References: <200803081133.02575.hselasky@c2i.net> <47D41160.9070901@elischer.org> <20080310105727.ah4y31sh40o04gw4@webmail.leidinger.net> In-Reply-To: <20080310105727.ah4y31sh40o04gw4@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803101751.48055.hselasky@c2i.net> Cc: freebsd-hackers@freebsd.org, Robert Watson , Julian Elischer Subject: Re: Documentation on writing a custom socket X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Mar 2008 17:50:46 -0000 ISDN can have more than 2-data channels per logical unit. There is something called E1 and T1 which has 30 and 24 B-channels respectivly per D-channel. --HPS On Monday 10 March 2008, Alexander Leidinger wrote: > Quoting Julian Elischer (from Sun, 09 Mar 2008 > > 09:33:36 -0700): > > Hans Petter Selasky wrote: > >> On Saturday 08 March 2008, Robert Watson wrote: > >>> On Sat, 8 Mar 2008, Hans Petter Selasky wrote: > >>> > >>> For example, do you > >>> anticipate using or even needing the routing facilities, and how might > >>> you map ISDN telephony parts into the normal network stack > >>> infrastructure of addresses, routing, interfaces, etc? > >> > >> Hi Robert, > >> > >> ISDN is very simple. In the ISDN world there is a term called TEI > >> which is the Terminal Entity Identifier. This kind of like an IP > >> address. > >> > >> Besides from the signalling there are 2 B-channels which can > >> transport data or audio. One of my goals is to achive zero copy > >> when moving data to/from an ISDN line and also in combination to > >> Voice over IP. Currently data is moved through userland (Asterisk > >> typically) which is usable in the short term, but in the long run I > >> want this extra copying removed. The idea is that I can route [IP] > >> packets (mbufs) through various filters in the kernel without the > >> need for copy. > > > > Given the speed of ISDN connections, It is not worth doing zero copy > > on ISDN unless you have more than 1000 of them, which seems unlikely. > > given a total throughput of 128000 b/s and the speed of current > > hardware, the number of packets per second is probably not high > > enough to make the difference even noticable. > > What about low-power embedded systems and a high count of small > packets (VoIP)? Where do you draw the line between powerful enough and > how do you chose this line? > > Bye, > Alexander.