d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add a simple netipx TODO list to the end of README, since there are a

Browse Source 
number of problems with netipx that I have not yet resolved, and I
don't want them lost track of.

MFC after:	1 month
This commit is contained in:
Robert Watson 2006-03-27 09:10:09 +00:00
parent 649814dd6c
commit e3c26fb50d
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=157175
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
sys/netipx/README
View File

@ -28,3 +28,22 @@ Modifications Copyright (c) 1995, John Hay
Modifications Copyright (c) 2004-2006 Robert N. M. Watson
*/
--- TODO ---
(1) netipx default socket buffer sizes are very small by contemporary
standards, and should be increased following testing and measurement.
(2) SPX will free the PCB and socket buffer memory on close(), which means
close() in effects terminates the transfer of any outstanding buffered
but unsent data. As with TCP, it should instead grab its own
reference to the socket so that it is not released, as hold onto it
until the data transfer is complete.
(3) Raw socket capture of IPX output intercepts packets in the SPX output
routine in order to feed them back into the raw socket. This results
in recursion into the socket code in the transmit path; instead,
captured packets should be fed into a netisr that reinjects them into
raw sockets from a new (asynchronous) context.
(4) IPX over IP encapsulation needs work to make it properly MPSAFE.