From owner-freebsd-net Thu Mar 1 6:31:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 20F5437B719 for ; Thu, 1 Mar 2001 06:31:15 -0800 (PST) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id PAA05613; Thu, 1 Mar 2001 15:30:52 +0100 (MET) Date: Thu, 1 Mar 2001 15:30:51 +0100 (CET) From: Harti Brandt To: Julian Elischer Cc: Marco Molteni , Subject: Re: How to implement a transport protocol with netgraph? (2) In-Reply-To: <3A9E597A.D3387FC2@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 1 Mar 2001, Julian Elischer wrote: JE>Harti Brandt wrote: JE>> JE>> I have implemented SSCOP for ATM signalling in netgraph lately. If it JE>> helps you, I can send you the current code. There are however still a JE>> number of issues: JE>> JE>> - It has no socket interface yet. I plan to do one base on the ng_socket JE>> code. There should be a lot of similarities. JE> JE>why can you not use the netgraph sockets? Well, I want to be able to say fd = socket(PF_ATM, SOCK_STREAM, ATMPROTO_SSCOP); or something along that line. And netgraph sockets didn't generate flow control messages when I last locked at them (three weeks ago). JE>> - How to do flow control is not very clear up to now. There are a number JE>> of messages defined in netgraph.h for this and I have used them, but JE>> had no time to do a thourough test. JE> JE>flow control has been added to -current using the messages you saw but JE>support is still not in most nodes. Only tee and UI nodes know how to pass them JE>on... JE> JE>hopefully people who find that node type 'X' blocks their flow control messages JE>can add the code to support them to 'X' and send me the diffs :-) JE> JE>I'm also looking to add some mechanism that makes this trivial but I JE>don't know what it will be yet. Well, the problem is with the semantics of those messages. TCP, for example, thinks in bytes, SSCOP thinks in messages. So you have to generate the flow control messages differently for different consumers. (Or have them support both types). harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message