From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 10 18:13:01 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 EA177106566B for ; Mon, 10 Mar 2008 18:13:01 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outZ.internet-mail-service.net (outZ.internet-mail-service.net [216.240.47.249]) by mx1.freebsd.org (Postfix) with ESMTP id B12E58FC35 for ; Mon, 10 Mar 2008 18:13:01 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Mon, 10 Mar 2008 11:13:01 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id E0B822D601F; Mon, 10 Mar 2008 11:12:58 -0700 (PDT) Message-ID: <47D57A33.1070209@elischer.org> Date: Mon, 10 Mar 2008 11:13:07 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Hans Petter Selasky References: <200803081133.02575.hselasky@c2i.net> <47D41160.9070901@elischer.org> <20080310105727.ah4y31sh40o04gw4@webmail.leidinger.net> <200803101751.48055.hselasky@c2i.net> In-Reply-To: <200803101751.48055.hselasky@c2i.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , Robert Watson , freebsd-hackers@freebsd.org 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 18:13:02 -0000 Hans Petter Selasky wrote: > 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. I know, but neither of these represent any challenge to modern hardware. > > --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. >