From owner-freebsd-hackers@FreeBSD.ORG  Sun Mar  9 09:26:37 2008
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 048FD1065671
	for <freebsd-hackers@freebsd.org>; Sun,  9 Mar 2008 09:26:37 +0000 (UTC)
	(envelope-from hselasky@c2i.net)
Received: from swip.net (mailfe07.swip.net [212.247.154.193])
	by mx1.freebsd.org (Postfix) with ESMTP id 8BF8E8FC15
	for <freebsd-hackers@freebsd.org>; Sun,  9 Mar 2008 09:26:35 +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 mailfe07.swip.net (CommuniGate Pro SMTP 5.1.13)
	with ESMTPA id 842121505; Sun, 09 Mar 2008 10:26:34 +0100
From: Hans Petter Selasky <hselasky@c2i.net>
To: Robert Watson <rwatson@freebsd.org>
Date: Sun, 9 Mar 2008 10:27:38 +0100
User-Agent: KMail/1.9.7
References: <200803081133.02575.hselasky@c2i.net>
	<20080308171435.J88526@fledge.watson.org>
In-Reply-To: <20080308171435.J88526@fledge.watson.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200803091027.39843.hselasky@c2i.net>
Cc: 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
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Mar 2008 09:26:37 -0000

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.

--HPS