Date: Thu, 28 Jan 1999 14:27:46 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Archie Cobbs <archie@whistle.com> Cc: hm@hcs.de, freebsd-isdn@FreeBSD.ORG Subject: Re: i4b and netgraph (was: I4B support for US ISDN?) Message-ID: <Pine.BSF.3.95.990128142128.11856E-100000@current1.whistle.com> In-Reply-To: <199901282115.NAA03956@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It's a dead snap.. On Thu, 28 Jan 1999, Archie Cobbs wrote: > Hellmuth Michaelis writes: > > When reading ftp://ftp.whistle.com/pub/archie/netgraph/man/netgraph.4.html, > > its easy to get that wrong impression: > > > > In order to minimize latency, all netgraph operations are functional. > > ^^^ > > That is, data and control messages are delivered by making function calls > > rather than by using queues and mailboxes. > > Yes, that's misleading... I've fixed it. > > Actually, it's not completely the way you want it yet. As it stands > now, when you send an mbuf, you have the option of either sending > it directly (ie, functionally) or sending it by queueing it for > delivery later. > > However, there's no way as the *receiving node* to say, "I want > all data sent to me to be delivered by qeueuing". So all sending > nodes would have to "cooperate". > > This ability would be easy to add and something we'll probably do > now that you've pointed it out. :-) I thought about this some time ago. Just add a method called "queued receive".. (rcvdataq). In most nodes this is filled out just the same as the rcvdata (or the dequeuer might check for a NULL and use rcvdata instead) In the case where node wants to force queuing, the normal rcvdata method simply calls ng_queue_data() as soon as it's called. The data is then queued and at dequeue time is fed in through rcvdataq() which actually accepts tha data. Note, that messages can also be queued. so a similar method may be used for that. > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.990128142128.11856E-100000>