home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip:3856 comp.protocols.pcnet:55
- Newsgroups: comp.protocols.tcp-ip,comp.protocols.pcnet
- Path: sparky!uunet!cs.utexas.edu!torn!watserv1!sail.uwaterloo.ca!eengelke
- From: eengelke@sail.uwaterloo.ca (Erick Engelke)
- Subject: Re: Clemson University Packet Driver: I have one problem B-(.
- Message-ID: <Bs2uvw.IKJ@watserv1.uwaterloo.ca>
- Sender: news@watserv1.uwaterloo.ca
- Organization: University of Waterloo
- References: <AJOhJRg8RQ@ntc.togliatti.su> <1992Jul27.072637.12601@medtron.medtronic.com>
- Date: Tue, 28 Jul 1992 02:28:42 GMT
- Lines: 32
-
- saty@ntc.togliatti.su writes:
-
- >>I write some application ( TSR type ) based on Packet Driver
- >>( Clemson University Engineering Comp Ops Version 9) and I have
- >>one tragic problem. I can not send ethernet packets while
- >>my receive handle works. How can I do it correctly?
-
- The 'preferred' solution is to not send the packet during the upcall
- but to schedule it for later.
-
- If you find 23 ms average delay acceptable, you can just transmit on
- the next timer tick.
-
- If you want faster response, use the packet driver GET_INFO function
- to ask the driver which hardware interrupt it generates. Then chain
- to that interrupt so it looks like this:
-
- pushf
- call dword old_irq_handler ; will be the packet driver
- ; now safe for us to do things
- jmp our_post_irq_handler
-
- This will invoke your routine immediately after the packet driver
- is done processing the interrupt, and you will have extremely small
- delays between receipt of packets and your reply.
-
-
- Erick
- --
- Erick Engelke Engineering Computing
- University of Waterloo
- Waterloo TCP Architect erick@development.watstar.uwaterloo.ca
-