mirror of
https://github.com/reactos/reactos.git
synced 2024-09-09 04:10:19 +00:00
e1ef078741
The idea then would be to have the following behaviour (when specifying the following options in the kernel command line): /DEBUGPORT=COMi --> load KDCOM.DLL and use COMi port (i == 1,2,3,4) if possible. /DEBUGPORT=FOO --> load KDFOO.DLL (useful for KDUSB.DLL, KD1394.DLL, KDBAZIS.DLL for VirtualKD, etc...) /DEBUGPORT=ROSDBG:[COMi|SCREEN|FILE|GDB|...] --> load KDROSDBG.DLL which contains the ROS kernel debugger, and use COMi or SCREEN or... as output port. svn path=/branches/kd++/; revision=58883
36 lines
922 B
Plaintext
36 lines
922 B
Plaintext
|
|
Ideas for optimizations:
|
|
|
|
* transmit.c (SendFragments, IPSendComplete):
|
|
Keep IPFRAGMENT_CONTEXT objects and PathMTU buffers in a pool
|
|
|
|
|
|
References:
|
|
|
|
RFC 791 - Internet Protocol
|
|
http://www.faqs.org/rfcs/rfc791.html
|
|
|
|
RFC 792 - Internet Control Message Protocol
|
|
http://www.faqs.org/rfcs/rfc792.html
|
|
|
|
RFC 793 - Transmission Control Protocol
|
|
http://www.faqs.org/rfcs/rfc793.html
|
|
|
|
RFC 826 - Ethernet Address Resolution Protocol
|
|
http://www.faqs.org/rfcs/rfc826.html
|
|
|
|
RFC 1122 - Requirements for Internet Hosts - Communication Layers
|
|
http://www.faqs.org/rfcs/rfc1122.html
|
|
|
|
RFC 1123 - Requirements for Internet Hosts - Application and Support
|
|
http://www.faqs.org/rfcs/rfc1123.html
|
|
|
|
RFC 2398 - Some Testing Tools for TCP Implementors
|
|
http://www.faqs.org/rfcs/rfc2398.html
|
|
|
|
RFC 2525 - Known TCP Implementation Problems
|
|
http://www.faqs.org/rfcs/rfc2525.html
|
|
|
|
RFC 2581 - TCP Congestion Control
|
|
http://www.faqs.org/rfcs/rfc2581.html
|