• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

READMED26-Jul-20151.4 KiB4230

ipx.cD26-Jul-201512.3 KiB462322

ipx.hD26-Jul-20157 KiB19586

ipx_cksum.cD26-Jul-20154.6 KiB14170

ipx_if.hD26-Jul-20155.5 KiB12938

ipx_input.cD26-Jul-201512.4 KiB469285

ipx_outputfl.cD26-Jul-20158.3 KiB288162

ipx_pcb.cD26-Jul-201512.2 KiB429290

ipx_pcb.hD26-Jul-20156.2 KiB15160

ipx_proto.cD26-Jul-20155.5 KiB16181

ipx_usrreq.cD26-Jul-201517 KiB687477

ipx_var.hD26-Jul-20155.4 KiB13054

spx.hD26-Jul-20158.4 KiB211111

spx_debug.cD26-Jul-20156.1 KiB197120

spx_debug.hD26-Jul-20154.1 KiB10432

spx_reass.cD26-Jul-201512.8 KiB452277

spx_timer.hD26-Jul-20156.7 KiB15030

spx_usrreq.cD26-Jul-201542.3 KiB1,7941,269

spx_var.hD26-Jul-20157 KiB16184

README

1$FreeBSD: stable/9/sys/netipx/README 194590 2009-06-21 16:11:26Z rwatson $
2
3This protocol implements IPX/SPX over Ethernet_II frame type 0x8137.
4Please note: the SPX implementation may require further work and testing
5to insure proper operation.
6
7Mike Mitchell, Network Engineer
8AMTECH Systems Corporation, Technology and Manufacturing
98600 Jefferson Street, Albuquerque, New Mexico 87113 (505) 856-8000
10supervisor@alb.asctmd.com
11
12John Hay
13Some Company
14Some Address
15jhay@mikom.csir.co.za
16
17Adapted for multi-processor, multi-threaded network stack by Robert N. M.
18Watson, Computer Laboratory, University of Cambridge.
19
20--- Copyright Information ---
21/*-
22
23Copyright (c) 1984, 1985, 1986, 1987, 1993
24The Regents of the University of California.  All rights reserved.
25
26Modifications Copyright (c) 1995, Mike Mitchell
27Modifications Copyright (c) 1995, John Hay
28Modifications Copyright (c) 2004-2009 Robert N. M. Watson
29
30*/
31
32--- TODO ---
33
34(1) netipx default socket buffer sizes are very small by contemporary
35    standards, and should be increased following testing and measurement.
36
37(2) SPX will free the PCB and socket buffer memory on close(), which means
38    close() in effects terminates the transfer of any outstanding buffered
39    but unsent data.  As with TCP, it should instead grab its own
40    reference to the socket so that it is not released, as hold onto it
41    until the data transfer is complete.
42